Skip to end of metadata
Go to start of metadata
WorkstreamAdded to the specification  / complete

(tick) Done

Ready for IRB Review 

(plus) Now

What We're Working on Today

(lightbulb) Next

Next Priorities*

Specification Content
Aggregate Reporting Workflows

Review to ensure mADX is included.  Change drawing to not assume that mADX/ADX report comes from HMIS.    

ICF / DASH (VLAD, JORGE)  HISP (BOB, AUSTIN)  HMIS SUB COMMUNITY

Add Spanish Version of the Diagram to the Specification

Begin to support the Spanish version of the diagram.  

  RI (JENNIFER AND MAURYA)   RECAINSA (JOSELINE)  
Insurance / Payer Workflows

Defining data exchanges. (Link)

 GIZ (UWE)  SWISS TPH (DRAGOS) 
CR Requirements

Review CR requirements to ensure PMIR and other FHIR standards are in there.  Check for changes due to CR offline transactions.  

PATH (LUKE)  IDENTITY COMMUNITY (SHAUN)

Workflow For Patient Follow up

 EMR ↔ Community system exchange for patient follow up (Link)

DIMAGI (MICHAEL) MEDIC MOBILE  

SHR Requirements

Redefine SHR requirements based upon FHIR

JEMBI (DANIEL) PATH (JOSE)  ICF / DASH (VLAD, JORGE)

Lab System Requirements

 Merging recent activities to define lab system requirements

ITECH / U WASH (JAN) RTI (RITA)  

pt-level data: Case Reporting Workflows

HIV Case reporting and COVID case reporting.

  PATH (JOSE)  JEMBI 
Pt-level data: SHR Workflows

Redefine SHR transactions based upon FHIR

JEMBI PATH  ICF / DASH


Privacy and Security Statement

Creating a statement for the Architecture Specification

UOO (BOB AND AUSTIN) RI (JENNIFER) 

French and Spanish version of the specification

Translation into French and Spanish

RI (MICHELLEJENNIFER) 

Product Catalog Requirements

Establish base requirements for the product catalogue.  

?  ?

Review Lab Workflows with OMRS team

Review OHIE lab workflows with OMRS team to see if there are changes, additions, clarifications   

RI (JEN, MAURYA)

Is an imaging point-of-care needed?


   

Specification Format

Better Linkage with FHIR IGs

Determine how to link FHIR IGs

  PATH (JOSE)  RI (JEN, MAURYA)  
Ownership of Content Sections

Determine and document ownership in the specification content sections.  

   RI (JEN, MAURYA)  
Better Link with IHE

Establish potential IHE roles for each architecture component.   

  PATH (JOSE)  RI (JEN, MAURYA) IHEUW (JAN, PIOTR)
Application Certification / Testing 

Document a Framework for Certification

Prepare and share a framework for talking about OHIE Certification  

    RI (SHAUN, JEN, MAURYA)   PATH (CARL F) UW (JAN, PIOTR)IHE ( ALEXANDER)
Role of Instant OpenHIE and IHE tools

Create a proposal for the roles of Instant OpenHIE, IHE and other tooling in the Data exchange Certification process.   

  IHE ( ALEXANDER)  RI (SHAUN, JEN, MAURYA)

PATH (CARL)  UW ( PIOTR, JAN)

Add Evaluation Criteria for "testing"

Determine how each requirement will be evaluated (method and criteria).  

  PATH (CARL F)   RI (JEN, MAURYA) UW (JAN, PIOTR)
Architecture Process  and People

ARB Make Up

Take a fresh look at ARB stakeholders and appropriate make up of the group.   

    RI (SHAUN, JEN, MAURYA)   PATH (CARL F) 

  • No labels

3 Comments

  1. I think it will be important to leverage our relationship with IHE to operationalize testing. They are notably absent from the testing activity. 

    1. IHE is engaged and working alongside RI, ITech and others.  IHE and was noted on some of tiles.  I have added them to the InstantOpenHIE tile as well.  This was an oversight. 

  2. Regarding FHIR IGs, have we begun to define which are our priority? To Derek's point, many IHE profiles leverage FHIR IGs so we may which to focus on both select profiles and their supporting HL7 IGs. Just a thought.