Versions Compared

Old Version 29

changes.mady.by.user Rick Freeman

Saved on

compared with

New Version Current

changes.mady.by.user Zoran Milosevic

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Technology and Architecture Committee 's purpose is to define a technical specification and logical architecture including the 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 integrations requirements that compliant HSPC platforms will implement and third party application developers will develop their applications against. This is the workspace of the committee and it's various workgroups containing meeting notes, project status, etc.

For documentation of the existing HSPC artifacts such as:

  • Building HSPC applications (tutorials and user forums)
  • Using the HSPC Sandbox
  • Downloading and installing the HSPC reference implementation
  • The HSPC Technical Specification

See our Developer Resources section in the main HSPC space.

The committee provides oversight to three focused workgroups:

HSPC Technical Specification Workgroup

The HSPC Technical Specification Workgroup are creating  

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. 

Image Added

HSPC Architecture Workgroup

Anchor
arch_work
arch_work

The Logica Architecture Workgroup are defining the spec App Developers and EHR Developers will implement to become HSPC enabled. Find the  

HSPC Technical Specification

 here in its current state

Workgroup

Anchor
arch_expr
arch_expr

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

The HSPC

Anchor
arch_manif
arch_manif

The Logica Reference Implementation Workgroup are working together to build the reference implementation of the HSPC 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

The HSPC

Anchor
arch_item
arch_item

The FHIR Sandbox Workgroup are working together to define the requirements of a sandbox, collect 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 host and support a sandbox. and foundational content to enable the sandbox's functionalities.  
For documentation about the current sandboxes go here.

 

The team