Architecture Governance and Principles
Architecture Meetings
Architecture Maturity
Release Management and Workflow Processes
Specification Documentation
OpenHIE IHE Integration Statements
OpenHIE Standards and Profiles
OpenHIE Privacy and Security
OpenHIE Planning and Implementation Guides
OpenHIE Reference Component Software
Reference Technologies
9 Comments
Carl Fourie
I like the new text here. This languages raises the question: "What if I only have some of the components? Is it still an OpenHIE architecture project?" I think we have a great chance to highlight that having an OpenHIE architecture doesn't mean needing all the components. .
pardha
Could you provide real epic for usage of TS component in in the above architecture?Whar are the spcicifications, protocols, where do we get the complete universal codes?
Jack Bowie
Terminology services are used in a number of the standard workflows, usually for validating codes. We do not as yet have a standard "starter set" of terminologies/codes available. The particular code systems that are required in an OHIE implementation are usually specified by the implementing organization, e.g., a country's Ministry of Health, so providing a "typical" set has proven difficult. Members of the Terminology Services community can assist you in locating any specific code systems you require. You can find further details on the considerations for code system selection and the recommended FHIR transactions for a Terminology Service in the Terminology Services Planning and Implementation Guide and associated documents, available on the Terminology Services page of this Wiki.
Jamie Thomas
Resource can be found here - https://wiki.ohie.org/display/SUB/Terminology+Service+Community
Vikas
What is the similarity/difference between HMIS within "external systems" and HMIS within "openHIE component layer"
Carl Fourie
HI Vikas
I'm not quite sure I understand your question fully?
Vikas
Hi Carl,
Sorry for not being clear. it was more of a thought when i wrote the message.
So the architecture shows HMIS under External system (below the interoperability layer) and OpenHIE component layer (above the IL). These two uses of the same term is confusing to me. We can still keep the same term if we have a clear definition of what is included in HMIS below the IL and above the IL. Does it make sense?
Thanks!
Carl Fourie
Hi Vikas
The way I've come to read this is that the HMIS can play both roles depending on the implmentation and architectural needs. For example: the HMIS can be a contributor/consumer of data from the HIE (this may be where the implementation of the HMIS is not within the mandate and control of the project), or it may be when data needs to flow between HMIS solutions (Such as the PEPFAR DATIM work where we see country to PEPFAR aggreatdate data exchanges as well as national to global etc).
The other is where the implementation of the HMIS is considered part of the broader HIE (under the same governance and focused on serving the business vision of the HIE).
That is more a personal view of how I'd read that and others from the HMIS community may describe it differently. Hope that helps
Jennifer E Shivers
The architecture pattern has been abstracted to meet multiple scenarios.
Here an example where there can be multiple HIMS systems involved in a single country's implementation:
A region in a country may have it's own HMIS that is required to collect data from various facilities in it's purview. That HMIS may then be required to send data to the national HMIS that is in the national HIE.
Carl also provided you with an example where the is a PEPFAR HMIS and a Country HMIS. In this case, it is likely that both HMIS systems could reside in different HIEs.
.