TY - GEN
T1 - Shared conceptual schema for four medical expert systems
AU - Held, James P.
AU - Carlis, John V.
PY - 1990
Y1 - 1990
N2 - The fundamental reason for database management systems is the support of applications using shared overlapping sets of data through external views of an underlying conceptual schema. The definition of such a schema for expert systems (ESs) is a topic of interest to database researchers both as a proof that ESs can be supported and as an exploration of the process of view integration. A shared conceptual schema has been constructed for four widely known medical ESs, and can be mapped to the knowledge base of each using seven operations: COMPOSE, FILTER, FOLD, UNFOLD, CONTRACT, RENAME, and CONSTRAIN. The schema and mappings show features the ESs share, such as rules and patterns, and features that distinguish them, such as a unique form of diagnosis. The schema's content shows a lack of structural, temporal, or strategic information and illustrates how the types and relationships of shell-like systems are hidden in instances and must be interpreted by program code.
AB - The fundamental reason for database management systems is the support of applications using shared overlapping sets of data through external views of an underlying conceptual schema. The definition of such a schema for expert systems (ESs) is a topic of interest to database researchers both as a proof that ESs can be supported and as an exploration of the process of view integration. A shared conceptual schema has been constructed for four widely known medical ESs, and can be mapped to the knowledge base of each using seven operations: COMPOSE, FILTER, FOLD, UNFOLD, CONTRACT, RENAME, and CONSTRAIN. The schema and mappings show features the ESs share, such as rules and patterns, and features that distinguish them, such as a unique form of diagnosis. The schema's content shows a lack of structural, temporal, or strategic information and illustrates how the types and relationships of shell-like systems are hidden in instances and must be interpreted by program code.
UR - http://www.scopus.com/inward/record.url?scp=0025694372&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=0025694372&partnerID=8YFLogxK
M3 - Conference contribution
AN - SCOPUS:0025694372
SN - 0818620250
T3 - Proceedings - Sixth International Conference on Data Engineering
SP - 410
EP - 419
BT - Proceedings - Sixth International Conference on Data Engineering
PB - Publ by IEEE
T2 - Proceedings - Sixth International Conference on Data Engineering
Y2 - 5 February 1990 through 9 February 1990
ER -