However, with increasing coverage of fields of anatomic pathology, such an interface terminology needs more rules and reference models than PathLex recently is based on. As interface terminologies in general, also PathLex is primarily aimed to enable an easy data entry at the front end of Pathology Reporting Systems. This reference model then can serve as a basis for a style guide for defining new terms in all fields of anatomic pathology.ĭue both to the complexity of SNOMED CT and gaps in LOINC and SNOMED CT for their use in recent anatomic pathology daily practice an interface terminology PathLex was developed by the IHE Anatomic Pathology Working Group. It describes a framework of classes of terms and the relationships between them as to represent concepts. The question is what are the generic aspects of each observation in anatomic pathology?īy analyzing the PathLex interface terminology and comparing it with the SNOMED-CT reference terminology, such a generic reference terminology model will be derived. The core principle of those models is the ontological structure of both "native speaking" terminology in anatomic pathology and its scientific background in the ontology of systemic pathology. This should a mapping to reference terminologies as part of the model of meaning make easier. As to enable a systematic approach for establishing rules for terminology development reference terminology models may help.
They are part of the model of use and have not been compiled in a systematic approach, therefore they gather terms of very different granularity and focus of interest. Current interface terminology systems for structured reporting in pathology, however, are more or less focussed on tumor pathology, and closely oriented on widely used templates for data entry, e.g. Interface terminologies are the best solution to bridge this gap. functions that involve storing, retrieving or processing application data, Īs long as reference terminologies such as SNOMED-CT are not widely available for end-users in record services, i.e. "To benefit from a terminology, it must be implemented and used as part of an application".
0 kommentar(er)
