Below is a list of presumptions around the terminology services layout that the OHIE-Terminology Services community is debating and cultivating.
| Info | ||
|---|---|---|
| ||
|
...
Dumb vs. Smart - Whether TS is a dumb (told what to do) or smart (see message and know what to do) service in relation to working with IOL?
...
SHR's vocab persistence model: single code or multiple codes?
...
Approaches to scalability?
The OHIE Terminology Service (TS) is assumed to be the source of truth for all terminology, nomenclature, and coded data within the OpenHIE shared health record. It will play a central role in terminology standardization and implementation throughout the HIE. However, it is only one component of the several components that comprise the OpenHIE. There are various ways the other components could interact with the TS. Here are some areas that the OHIE-Terminology Services community has been discussing.
Please note that the Google Doc below can be used to add comments/feedback for discussion. Access the live document via this link.
| Iframe Macro | ||
|---|---|---|
| ||
...