Skip to:
The I_TERMINOLOGY interface is not yet defined here https://specifications.openehr.org/releases/SM/latest/openehr_platform.html
Some suggestions for terminology use cases that might help 1. defining the interface and 2. create a conformance spec for that component:
+ return part of one terminology
a "part" could be a domain, a chapter, a subset, etc.
this includes codes, rubrics and definitions if available+ retrieve descendants, given one terminology item
this applies only for hierarchical terminologies
a terminology item could be given by any of it's identifiers in the correspondent terminology+ retrieve ancestors, given one terminology item
a terminology item could be given by any of it's identifiers in the correspondent terminology+ offer suggestions based on given text
text might be partial, complete or acronym
current language is needed as context
part of the terminology might be required to give context and constraint results
queried terminology is required+ retrieve mappings of terminology items between different terminologies
given a terminology term, it's terminology and the target terminology, retrieve the matching terminology items from the target terminology
The I_TERMINOLOGY interface is not yet defined here https://specifications.openehr.org/releases/SM/latest/openehr_platform.html
Some suggestions for terminology use cases that might help 1. defining the interface and 2. create a conformance spec for that component:
+ return part of one terminology
a "part" could be a domain, a chapter, a subset, etc.
this includes codes, rubrics and definitions if available
+ retrieve descendants, given one terminology item
this applies only for hierarchical terminologies
a terminology item could be given by any of it's identifiers in the correspondent terminology
+ retrieve ancestors, given one terminology item
this applies only for hierarchical terminologies
a terminology item could be given by any of it's identifiers in the correspondent terminology
+ offer suggestions based on given text
text might be partial, complete or acronym
current language is needed as context
part of the terminology might be required to give context and constraint results
queried terminology is required
+ retrieve mappings of terminology items between different terminologies
given a terminology term, it's terminology and the target terminology, retrieve the matching terminology items from the target terminology