Building on from the Defining an Open Platform paper by Apperta
In line with the principle that an open source reference implementation is needed to prove/educate others in any technology.. here we list the key components needed by the community
A Terminology Service serves as a central authority to uniquely identify the clinical activities that occur within the care delivery process by maintaining a terminology set mapped to international standards such as ICO10, LOINC, SNOMED, and others – “What?”
An enterprise master patient index (EMPI), or Client Registry manages the unique identity of citizens receiving health services with the country – “For whom"
A Shared Health Record (SHR) is a repository containing the normalized version of content created within the community, after being validated against each of the previous registries. It is a collection of person-centric records for patients with information in the exchange.
A Health Management Information System (HMIS) stores routinely-collected aggregate health care data, and facilitates their analysis with the goal of improving the quality of health services.
A Health Facility Registry serves as a central authority to uniquely identify all places where health services are administered within the country – “Where?”
A Health Worker Registry is the central authority for maintaining the unique identities of health providers within the country – “By whom"
A Health Interoperability Layer receives all communications from external services within a health geography, and orchestrates message processing among the external systems and the OpenHIE component layer.
These inputs fed into this list to be debated/discussed & actioned on
Infrastructural Components of Open Platform - for action
.. which then are combined to develop showcase applications aka
Innovation Implementations of Open Platform - in action
eg
Personal Held Records
Electronic Patient Records
Integrated Digital Care Records
NB this issue may work better as a related wiki entry? Feedback welcome on this please
Building on from the Defining an Open Platform paper by Apperta In line with the principle that an open source reference implementation is needed to prove/educate others in any technology.. here we list the key components needed by the community
Informed by list drawn up from earlier 1% Open Platform push (see Appendix 1) http://ripple.foundation/2017/01/open-digital-platform-challenge-fund/
Identification & Authorisation
Master Patient Index
User Interface framework
Integration technologies
Clinical Data Repository
Terminology services
Workflow services
Rules engine
Scheduling
Business intelligence
Clinical content collaboration/authoring tools (i.e. openEHR/FHIR etc)
informed by leading work of openHIE group & their approach to reference technologies https://wiki.ohie.org/display/documents/Reference+Technologies
A Terminology Service serves as a central authority to uniquely identify the clinical activities that occur within the care delivery process by maintaining a terminology set mapped to international standards such as ICO10, LOINC, SNOMED, and others – “What?”
An enterprise master patient index (EMPI), or Client Registry manages the unique identity of citizens receiving health services with the country – “For whom"
A Shared Health Record (SHR) is a repository containing the normalized version of content created within the community, after being validated against each of the previous registries. It is a collection of person-centric records for patients with information in the exchange.
A Health Management Information System (HMIS) stores routinely-collected aggregate health care data, and facilitates their analysis with the goal of improving the quality of health services.
A Health Facility Registry serves as a central authority to uniquely identify all places where health services are administered within the country – “Where?”
A Health Worker Registry is the central authority for maintaining the unique identities of health providers within the country – “By whom"
A Health Interoperability Layer receives all communications from external services within a health geography, and orchestrates message processing among the external systems and the OpenHIE component layer.
These inputs fed into this list to be debated/discussed & actioned on Infrastructural Components of Open Platform - for action
.. which then are combined to develop showcase applications aka Innovation Implementations of Open Platform - in action eg Personal Held Records Electronic Patient Records Integrated Digital Care Records
NB this issue may work better as a related wiki entry? Feedback welcome on this please