| Workstream | Added to the specification / complete |
Ready for ARB Review |
What We're Working on Today |
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 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) French and Spanish version of the specification Translation into French and Spanish RI (MICHELLEJENNIFER) | 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 (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. SAMSON J 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 RI TEAM | 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 TEAM Document Key Use Cases Determine a process for documenting the use cases for each of the data exchanges ARCHITECTURE LEAD TEAM |
| Specification Format | Better Linkage with FHIR IGs | Ownership of Content Sections Determine and document ownership in the specification content sections. ARCHITECTURE LEADSBetter 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 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 the Architecture Meeting structure and propose a path forward RI TEAM PATH (CARL F) | Architecture Leads Determine who needs to participate in the Architecture Leads RI TEAM PATH (CARL F) | ||
| DevOPS | ARB Make Up Figure out a way to tag projects in GitHub as well as tagging FHIR IGs SOVELLO AND DEVOPS |
Done
Now
NextOverview
Content Tools