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

Where: Google Hangout  

Participants: Larry, Roger, Knut, Niamh, Scott

Recorded Video:

Agenda:

  • Identifying a first workflow and moving forward on drafting it together.
  • Updates on the Facility Registry Implementer Call Moving Forward
  • AOB as time allows (Some potential things include: Implementation updates, implementers guide, facility data to support the Ebola outbreak response, and whatever your burning issues are.)

Outcomes:

Goal for the Workflow #1:

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

  • Roger/Niamh: See some definition between a TS and code sets used in a FR?   Push most in TS except many the hierarchical service may not be well capable.   The initial limitation was -> Hierarchy operations and moving branches of trees that terminology servers are set up to do.  Also, we haven't addressed the issue of multiple hierarchies … ( not sure if a TS could prevent data challenges)

    • 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,

  • Knut

    • Resonates well… often see that is a mess in most countries

    • There is no agreed to coding

      • 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

    • Especially a problem in countries where the script is not like english

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

        • Code sets

        • Facilities

        • Tools??

    • WHO - SARA (Service Availability and Readiness Assessment)

      • Standard ones up on a TS

      • Can we help to take this and put it up as an input to requirements gathering that a country does.

      • Can we also use it in the context of supporting countries to define their requirements and where their overlaps is aligned with requirements

    • Map code sets

      • Between standards or between languages

  • Niamh

    • Integrating with DHIS and they have 1 way to categorize ownership and if that can be harmonized .  If it is run by the

  • Larry

    • CSD -> Facility X … what are the services.  Which providers are at that facility

    • This work flow could benefit: There would be a standardized way to define what services are there … instead of a hodgepodge of codings defined by the country. CSD Workflow?  

Roger

    • Granularity of services:   Is there a single list that everyone users?   HIV services that are offered --- there is a standard list used in the US

    • Certified … for types of services … required for

    • Implementation question as there are different levels of details and uses.  

  • Larry

    • Some of the other communities are saying that things have to go through the IL to get to the TS???

Developers vs. Architects vs. Project Managers vs.

  • A challenge in TZ … Not too enthusiastic about western led initiatives

  • HISP: Doesn’t do a lot of calls, relys on workshops and mailing list

    • Maybe a Conference Line


  • No labels