...
- Conformance testing/certification environment
Two Tiers of the Technical Specification, Two Tiers of Sandboxes
The team agreed that there will be two tiers of the technical specification.
Tier 1
- Define a consistent way to read, write, and update data. Including:
- Clinical datatype structural and terminology definition
- Query language and supported criteria for filtering
- Define how hosting EMRs will launch HSPC applications
- Authorization
- Authentication
- Application Launch Context
- Clinical Event Manager
- Pub/Sub model for application
- Define set of required events
Tier 2
- Requires all specifications defined in tier 1 to be implemented
- Define workflow and SOA features to enable advanced clinical application development
Since there are two tiers of the technical specification, a sandbox may either be a Tier 1 or a Tier 2 implementation of the specification. Note that being a Tier 2 implementation implies that the sandbox supports all the requirements of a Tier 1 implementation.
Existing Tier 1 sandboxes
- ASU: FHIR services: conditions, obervations, medications, etc.
- iSalus: Current on tech spec reference implementation (Authen, Author, FHIR Svc)
Next Steps
- Team to meet Friday, September 19th at 8:30 MDT to discuss next steps to building out a Tier 1 & Tier 2 sandbox. Rick Freeman
- Aziz Boxwala, Scot Post van der Burg, and Marc Waterloo to meet to discuss current state of the Tier 1 specification and what they would need to implement it. Scot Post van der Burg (Unlicensed)
- Profiles discussion w/Tom Rick Freeman
- Consoliate ASU and iSalus sandboxes. Rick Freeman, RobertG (Unlicensed)
- Investigate collection of test data. Herb White (Unlicensed)