2014 Technical Development Roadmap
| March | * Design save encounter workflow * Design query encounter workflow * Work to implement save encounter workflow |
| April | * Design save encounter workflow * Design query encounter workflow * Work to implement save encounter workflow |
| May | * Design send aggregate data to HMIS workflow * Work to implement save encounter workflow * Work to implement query encounter workflow
|
| June | * Design send aggregate data to HMIS workflow * Work to implement query encounter workflow |
| July | * Design send aggregate data to HMIS workflow * Work to implement aggregate data workflow |
| August | * Work to implement aggregate data workflow |
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
...
Use Cases and Requirements
- Shared Health Record Functional Specifications
SHR - Use Cases and Requirements
- Version 1 (Needs Revision)
- Facets of an SHR
A discussion document highlighting:
- Different approaches : Document Based vs Discrete Data Based vs Hybrid
- A list of needs from the point of view of different stakeholders
- Technology considerations
See also: Primary Use Cases of OpenHIE
Adding Integrated Care Pathways to OpenHIE.pptx
Architecture and Design Specification
Current:
Previous iterations:
Supported Workflows
- Save patient-level clinical data workflow - V1.0
- Query patient-level clinical data workflow - V1.0
- Send health worker alert workflow
...
Standards
https://wiki.ohie.org/display/SUB/OpenSHR+-+Initial+Designs+-+Indianapolis+Feb+2013
OpenMRS as the SHR design document
Current:
Background documents:
...
...
...
- - The CSD profile supports queries across related directories containing data about: organizations, facilities, services and providers.
Message specifications
Discussions
- See the Legacy Discussion Doc for various comments and discussions related to the OpenSHR
- Clinical Decision Support
- OpenSHR Indy Meeting Feb 2013 Outcomes
- How do we define an encounter?