Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

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:

  • How to create HSPC enabled applications or platforms
  • HSPC Sandboxes
  • The HSPC Technical Specification
  • The HSPC Tier 1 Reference Implementation

See our Developer Resources section in the main HSPC space.

HSPC Technical Specification Workgroup

The HSPC Technical Specification Workgroup is creating the spec App Developers and EHR Developers will implement to become HSPC enabled. Find the /wiki/spaces/HSPC/pages/6717442 here in its current state.

HSPC Reference Implementation Workgroup

The HSPC Reference Implementation Workgroup is working together to build the reference implementation of the /wiki/spaces/HSPC/pages/6717442. Once the Tier 2 specification starts to take shape, this workgroup will also work to build that as well. For information about the HSPC Tier 1 Reference Implementation, including how to download, build, and install it, go here.

HSPC Sandboxes Workgroup

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.

Platform and Application Integration Framework Workgroup

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.

 

  • No labels