# data[].attributes.headline
Foundations for HIE implementation to demonstrate interoperability value

# data[].attributes.subject
Foundations for HIE implementation to demonstrate interoperability value

# data[].attributes.body
How to scope an HIE implementation- based on priority needs, Attestation of Software/platforms capabilities to meet defined requirements, How to identify and/or build core skills for implementation- will be great if this is mapped to existing platforms, standards, metadata (terminology/data elements) management, security.

# data[].attributes.body
What good data governance looks like, how to hire, how to measure performance

# data[].attributes.body
As we discussed in the Security and Privacy group call, it seems that there is no OpenHIE-wide glossary of terms and definitions which could be used for writing documentation (not to be confused with Terminology Services). // submitted by Michael M.

# data[].attributes.body
I think we need to put in active effort to review implementations to see where there are deviations from the workflow specifications. Then work to refine the workflows to reflect what tends to be the necessary in a real world implementation.

# data[].attributes.body
Use-cases, value, workflows to specific systems, example SOP for data governance

# data[].attributes.body
Scope and time available to manage OpenHIE channels among the different systems.

# data[].attributes.body
How to get funding for sandboxing of interoperability development without having an implementation in the field?

# data[].attributes.body
Status:  Implemented
Use-case: National Product Catalog, GTIN lookup, integration scope TBD

# data[].attributes.body
Published National Classification of Diseases

# data[].attributes.body
Status:  in-progress
Use-Case: Zanzibar Product Catalog, scope TBD.

# data[].attributes.body
Status: Implemented
Use case: National Product Catalog, GTIN lookup, integrating to central warehousing

# data[].attributes.body
Status:  Implemented
Use case: National Product Catalog, GTIN lookup, customs

# data[].attributes.body
Implemented
Use case:  National Product Catalog, starting at GTIN lookup

# data[].attributes.body
(Very fresh) Sri Lanka is proposing to set up a virtual server to implement and test OCL as their terminology service, which will include multiple terminologies like: ICD-10, ICPC-3, LOINC, LIFE (Lanka Interoperability Framework), and Code systems and value sets as per SL Core FHIR profiles

# data[].attributes.body
Exchange of openIMIS with payment layer, AfyaCare, GoTHOMIS

# data[].attributes.body
5 councils using iHRIS to exchange health worker data and create one 'source of truth'

# data[].attributes.headline
GOFR is being added to the OpenELIS central sever stack

# data[].attributes.subject
GOFR is being added to the OpenELIS central sever stack

# data[].attributes.body
This means it will be used as the FR in Côte d’Ivoire and Mauritius

# data[].attributes.body
Ethiopia have deployed a regional data repository for reporting purposes (basically SHR + HMIS) they are now interested in considering a national system.

# data[].attributes.body
Have some immediate need for dataset de-duplication but are also interested in a more complete CR solution. However, there are strict restriction on what demographics may be captured.

# data[].attributes.body
Nationla Health Insurance Board is accepting / requiring FHIR eClaims from Hospital Management Systems

# data[].attributes.body
It seems like implementers are commonly saying that they want to get started with a TS but do not necessarily know where to start. We often recommend scoping out their project and having specific use cases where the TS will come into play. Is there a way we can help streamline this process for getting started?

# data[].attributes.body
Use cases/case studies relevant to LMICs

# data[].attributes.body
Access to reference vocabs and local terminologist capacity remain obstacles -- limited case studies for LMIC terminology implementation to guide implementers

# data[].attributes.body
Forum for terminology services implementation discussions - Terminology Implementer series

# data[].attributes.body
Use case: "Develop, publish, and maintain a nationally harmonized concept dictionary to provision terminologies for local EMR implementations that will serve as the foundation for an emerging National Health Data Dictionary (NHDD) that enables a variety of data exchange needs within Kenya’s health information architecture."

# data[].attributes.body
Organizational issues within the implementation team, as well as a poor understanding of the key attributes of an HIE-in general.

# data[].attributes.body
Patient registry serving the Uganda Cancer Institute

# data[].attributes.body
In testing stage (as of March 2022)

# data[].attributes.body
MoH CR
(Data Lake) Demographic Data Exchange and Client Registry - national scale up

# data[].attributes.body
In the tooling decision stage (as of March 2022)

# data[].attributes.body
National implementation.
In process to take full advantages of biometrics.

# data[].attributes.body
Status:  Doing a requirements and planning workshop in 2022-oct
Use cases:  Unknown
Global Good Use: Unknown

# data[].attributes.body
to add a new sticky note you can use the plus sign (+) in the bottom right corner or double click anywhere on the corkboard

# data[].attributes.attachment_link.readable_text
RECORDING

Join from PC, Mac, Linux, iOS or Android: https://iu.zoom.us/j/832179402?pwd=SHAzL1kwTmcyYm1PdkdzNVNLNUZ6dz09

Or Telephone: Dial: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)

Meeting ID: 832 179 402 Passcode: 1

International numbers available: https://zoom.us/u/c1Vz5ASHm

You can also access the notes below here.

# data[].attributes.attachment_link.title
2022-10-28 OHIE Quarterly Subcommunity Alignment

# data[].attributes.attachment_link.description
RECORDING Join from PC, Mac, Linux, iOS or Android: https://iu.zoom.us/j/832179402?pwd=SHAzL1kwTmcyYm1PdkdzNVNLNUZ6dz09 Or Telephone: Dial: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll) Meeting ID: 832 179 402 Passcode: 1 International numbers available: https://zoom.us/u/c1Vz5ASHm You can also access the notes below here.

# data[].attributes.body
What countries are implementing (planning, implementing or have implemented) the component and what use cases are they trying to address

# data[].attributes.body
What are the key challenges that implementers are facing

# data[].attributes.body
What changes or additions are needed in OpenHIE documentation / materials (what is missing or incorrect)