The Technology and Architecture Committee 's purpose is to define the a logical service-oriented architecture, an endorsed content model and a technical specification to support interoperable applications. The recommendations of this Committee include service definitions, security model, eventing, and User Interface user interface integrations requirements supporting that compliant HSPC EMRs platforms will implement and consuming third and third party application developers can will develop their applications against.
HSPC Technical Specification
The HSPC Technical Specifications space details the requirements to which implementing HSPC enabled applications and platforms adhere. Additionally, current agenda and project planning surrounding the process of building out the specifications can be found there.
Platform and Application Integration Framework
The HSP Platform and Client Integration Frameworks space details the architecture and design of the integration framework, the current project status and planning, links to source code, and various developer resources needed to utilize the frameworks or contribute to the process of developing these frameworks.
HSP Reference Implementation
The HSP Reference Implementation space details the architecture and design of the integration frameworks, the current project status and planning, installation and use documentation, links to source code, and information on how to contribute to the development of the reference platform and EMR.
HSP Demo & Development Sandboxes
The HSPC Sandboxes space provides information about existing HSPC platform and EMR sandboxes as well as current project status and planning surrounding the deployment of new sandboxes.
Blog stream
| Blog Posts | ||||
|---|---|---|---|---|
|
Space Table of Contents
Please note that, while this paged is aimed at architects and system integrators, detailed developer resources can be found /wiki/spaces/OR/pages/6717453.
HSPC Architectural principles
HSPC adopts a 4-layer model :
- A common, logical architecture model
This is where the relevant functional requirements, capabilities, content models and their interactions and inter-dependencies are defined
By mission, the HSPC architecture is open, service oriented, model and knowledge driven.
- One or more platform-independent architectural specifications
Matching the overarching logical architecture, this is the level where standards will be adopted.
HSPC will then endorse one reference architecture.
- One or more platform-specific implementations
For any given architecture, platform-specific technologies will be adopted for concrete implementation purposes.
HSPC will provde at least one reference implementation of the reference architecture
- One of more installations
Implementations will be deployed at various sites for development, testing, or even production purposes.
HSPC will maintain a reference sandbox installation of its reference implementation.
HSPC Architecture Workgroup
| Anchor | ||||
|---|---|---|---|---|
|
The Logica Architecture Workgroup are defining the spec App Developers and EHR Developers will implement to become HSPC enabled.
HSPC Technical Specification Workgroup
| Anchor | ||||
|---|---|---|---|---|
|
The Logica Technical Specification, in its evolving state, reflects the HSPC endorsed standards and technologies for the creation of
the service oriented platform which supports the HSPC compliant applications.
HSPC Reference Implementation Workgroup
| Anchor | ||||
|---|---|---|---|---|
|
The Logica Reference Implementation Workgroup are working together to build the reference implementation of the Logica Technical Specification.
For current documentation about the existing HSPC Reference Implementation, including how to download, build, and install it, go here.
HSPC Sandboxes Workgroup
| Anchor | ||||
|---|---|---|---|---|
|
The FHIR Sandbox Workgroup are working together to define the requirements of a sandbox, to host and support the HSPC Reference implementation on a cloud-based platform.
The Workgroup is also focused on collecting useful de-identified clinical data and foundational content to enable the sandbox's functionalities.
For documentation about the current sandboxes go here.
The team
- Rick Freeman (interim convener)
- RobertG (Unlicensed)
- Craig Parker, MD
- Herb White (Unlicensed)