When: 10/16/2014 at 11:00 AM EDT

Where: Google Hangout  

Participants: 

Recorded Video:

Agenda:

• Workflow for Code sets to be uploaded to a FR: Clarifying any remaining requirements and beginning to determine the specifications/transactions/components needed...

• Identify ways this community can support the Ebola response via Facility Registries or improving facility data availability. I would propose we start by identifying any current needs and see what next steps we might be able to identify.

• AOB / Implementation Updates as of interest

Outcomes:

Workflow - Codeset Sharing User Stories

• User story: As a government user I want to redefine admin hierarchy level, as my country evolves, and have that reflected in my tools, to

• User Story: Multiple hierarchies need to be managed,

• User Story: Some actor(s) in a country is responsible for codeset/standards, I have no source of truth to manage code sets important to FRs

• User Stories: In TZ, There were many code sets managing different lists.  Understanding core data elements and how they can improve roles and responsibilities

• User Story: Users localization and internationalization across languages and scripts

• Code sets

• Facilities

• Tools??

• User Stories: I need to help manage hierarchical and flat

Questions….

Q1: Any proven existing methods for doing this?

• Sweden … Might be a good (http://www.geonames.org/NO/administrative-division-norway.html) & (http://en.wikipedia.org/wiki/ISO_3166-2)
• Native API - From Apelon … I wonder what specification
• Struggles to handle hierarchical code sets
• FR might be a good place to hold this
• Being sorta used by OpenHIE
• DHIS solution in the future on the roadmap

Q1.1: What should be the source of truth?

•  SA as an example with DHIS
•  Location Registry similar to bangladesh
•  Could a Facility Registry be the source (Use a Rest Interface?)
•  Should be TS?

Q1.2: Does the hierarchy include the facility and sub-levels,

Q2: How should we engage with the TS community?

• Go to their call
• Define a hierarchy fields
• Would it be possible to have a short list of things to keep?
• Administrative Hierarchy (MOH / PMORALG)
• Other partner hierarchies …  (Census Group/NIMR)
• ICD-10?  
• ICHI might be an option in the future … or DHIS ICD-10 code…

Q3:  Is there a need for consumers of the FR to better understand the metadata?  

•  https://github.com/facilityregistry/fred-api/issues/57

Q4: Any ideas on standards to consider?  (FHIR, otherwise?)

Q5: How would the FR tool incorporate it into a data structure

• You wouldnt want to automatically display the new
• You may want to track changes
• Need some way to show new and old context …