The Technology and Architecture Committee's purpose is to define the service definitions, security model, eventing, and User Interface integrations requirements supporting HSPC EMRs will implement and consuming third party application developers can develop their applications against. This is the workspace of the committee and it's various workgroups containing meeting notes, project status, etc.
For information on:
See our Developer Resources section in the main HSPC space.
The HSPC Technical Specification Workgroup is creating the spec App Developers and EHR Developers will implement to become HSPC enabled. Find the HSPC Tier 1 Technical Specification here in its current state.
The HSPC Reference Implementation Workgroup is working together to build the reference implementation of the HSPC Tier 1 Technical Specification. Once the Tier 2 specification starts to take shape, this workgroup will also work to build that as well.
The HSPC Sandbox Workgroup space provides information about existing HSPC platform and EMR sandboxes as well as current project status and planning surrounding the deployment of new sandboxes. For information about the current sandboxes go here.
The HSPC Platform and Client Integration Workgroup is working together to create a set of libraries to speed the effort of integrating existing applications and EHR/EMRs to become HSPC enabled. Much like the Spring Framework provides libraries the eliminate boilerplate code allowing developers to focus on their project rather than the nuances of connecting to a JMS queue, for example, these libraries are meant to do the common work that most platform implementors or app developers would have to do.