|Workstream||Added to the specification / complete|
Ready for ARB Review
What We're Working on Today
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)
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)
French and Spanish version of the specification
Translation into French and Spanish
Workflow For Patient Follow up
EMR ↔ Community system exchange for patient follow up (Link)
DIMAGI (MICHAEL) MEDIC MOBILE
Redefine SHR requirements based upon FHIR
JEMBI (RYAN) PATH (JOSE) ICF / DASH (VLAD, JORGE)
Pt-level data: SHR Workflows
Redefine SHR transactions based upon FHIR. Is the component a SHR or does the picture need a patient-level data repository as well?
JEMBI PATH ICF / DASH
pt-level data: Case Reporting Workflows
HIV Case reporting and COVID case reporting.PATH (JOSE) JEMBI
Lab System Requirements
Merging recent activities to define lab system requirements
ITECH / U WASH (JAN) RTI (RITA)
Is an imaging point-of-care needed?
Establish a community or working group to address how imaging fits into the Architecture.
Privacy and Security Statement
Creating a statement for the Architecture Specification
UOO (BOB AND AUSTIN) RI (JENNIFER)
Privacy and Security Statement
Change the wording for "Workflow" per meeting comments from 2022-10-10 OHIE Architecture Call
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
Document Key Use Cases
Determine a process for documenting the use cases for each of the data exchanges
ARCHITECTURE LEAD TEAM
Better Linkage with FHIR IGs
Determine how to link FHIR IGsPATH (JOSE) ARCHITECTURE LEADS
Ownership of Content Sections
Determine and document ownership in the specification content sections.ARCHITECTURE LEADS
Better Link with IHE
Establish potential IHE roles for each architecture component.PATH (JOSE) RI TEAM IHEUW (JAN, PIOTR)
|Application Certification / Testing|
Document a Framework for Certification
Prepare and share a framework for talking about OHIE CertificationRI (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 the Architecture Meeting structure and propose a path forwardRI TEAM PATH (CARL F)
Determine who needs to participate in the Architecture LeadsRI TEAM PATH (CARL F)
Identify Projects and FHIR IGs
Figure out a way to tag projects in GitHub as well as tagging FHIR IGsSOVELLO AND DEVOPS
Derek Ritz (ecGroup)
I think it will be important to leverage our relationship with IHE to operationalize testing. They are notably absent from the testing activity.
Jennifer E Shivers
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.
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.