A
B
C
Codebase
The HSPC Reference Implementation and all of the HSPC applications, tools, and services are open source using the Apache 2 license. You can find the source code here: https://bitbucket.org/account/user/hspconsortium/projects/PROJ
D
E
F
FHIR
See HL7 FHIR.
FHIR Client
See SMART FHIR Client and HSPC Java Client Library.
FHIR Database
A database that stores FHIR resources. A FHIR database should be accessed through a FHIR Resource API server.
FHIR Profiles
See HSPC FHIR Profiles.
FHIR Resource API Server
A FHIR Resource API Sever is a web endpoint that supports the FHIR API specification. A FHIR Resource API Server is generally backed by a database. However, the backing system may directly store FHIR resources or may provide an adapter to a legacy or proprietary datasource (such as a real-world EHR system).
G
H
HL7 FHIR
HL7 FHIR, or FHIR, is the healthcare system standard for exchanging information between separate healthcare systems. HSPC strives to be compatible with the current release version of FHIR.
HSPC Ecosystem
The HSPC Ecosystem is composed of the project initiatives, software systems, industry specifications, galleries, reference implications, and applications for the consortium.
HSPC FHIR Profiles
HSPC is actively producing a large set of FHIR Profiles. You can find more details in the Modeling and Terminology Initiatives project space.
HSPC Java Client Library
The HSPC Java Client Library is an open source implementation of the SMART on FHIR client specification.
HSPC Patient Data Manager
The HSPC Patient Data Manager is a provider facing, patient context SMART on FHIR app that allows a user to browse and modify clinical and demographic data for a patient.
HSPC Reference Implementation
The Logica Reference Implementation is an implementation of the HSPC Technical Specification (including SMART on FHIR and FHIR DSTU2).
HSPC Sandbox
The Logica Sandbox is a site where users can create sandbox instances. A sandbox instance is a personal instance of the HSPC Technology Stack including the HSPC Reference Implementation, a FHIR database, and a registry for the user's apps.
HSPC Technical Specification
The Logica Technical Specification describes the platform, technologies, and tiers of the HSPC ecosystem.
HSPC Technology Stack
The HSPC Technology Stack is an open-source implementation of the HSPC Technical Specification. The HSPC Technology Stack includes the HSPC Reference Implementation, the HSPC Sandbox, and the HSPC Tools Suite.
HSPC Tools Suite
The HSPC Tools Suite consists of the tools created by HSPC Development for the purpose of enabling the creation, testing, and marketing of SMART on FHIR apps. Tools include the HSPC Patient Data Manager.
HTTP/HTTPS
HTTP and HTTPS are application protocols for distributed, collaborative, hypermedia information systems. HTTPS (also called HTTP over TLS, HTTP over SSL, and HTTP Secure) is a protocol for secure communication over a computer network which is widely used on the Internet. HSPC uses HTTP/HTTPS as the transport protocol for communication between apps, resource servers, and authorization servers.
I
J
Java Client Library
JSON
JSON (JavaScript Object Notation) is a lightweight data-interchange format.
JWT
JSON Web Token (JWT) is a compact URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is digitally signed using JSON Web Signature (JWS).
K
L
Launch Scenario
A launch scenario is a mechanism of the HSPC Sandbox allowing an application to be repeatably launched using the same conditions. For example, the same practitioner, the same patient, the same launch parameters and the same app.
LOINC
LOINC is a universal code system for tests, measurements, and observations.
M
N
O
OAuth 2.0
OAuth 2.0 is the next evolution of the OAuth protocol which was originally created in late 2006. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices. The HSPC Technical Specification uses OAuth 2.0 for authorization.
OpenID Connect
OpenID Connect is a simple identity layer on top of the OAuth 2.0 protocol. It allows Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner. The HSPC Technical Specification uses OpenID Connect for identity.
P
Q
R
Reference Implementation
See HSPC Reference Implementation.
RxNorm
RxNorm provides normalized names for clinical drugs and links its names to many of the drug vocabularies commonly used in pharmacy management and drug interaction software, including those of First Databank, Micromedex, MediSpan, Gold Standard Drug Database, and Multum. By providing links between these vocabularies, RxNorm can mediate messages between systems not using the same software and vocabulary.
S
Sandbox
A sandbox is created by a user on the HSPC Sandbox site. A sandbox is a personal instance of the HSPC Technology Stack and a registry for the user's apps.
SMART
SMART (Substitutable Medical Applications & Reusable Technologies) is a group from Boston Children’s Hospital Computational Health Informatics Program and the Harvard Medical School Department of Biomedical Informatics.
SMART FHIR Client
The SMART FHIR client is a JavaScript client library for SMART on FHIR apps from the SMART team.
SMART on FHIR
SMART on FHIR is an app platform for healthcare. SMART on FHIR provides a specification for integrating apps with Electronic Health Records, portals, Health Information Exchanges, and other Health IT systems. HSPC uses the SMART on FHIR specification for app development.
SMART Python Client
The SMART Python client is a Python client library for SMART on FHIR apps from the SMART team.
SMART SWIFT Client (iOS)
The SMART SWIFT client is a SWIFT client library for SMART on FHIR apps from the SMART team.
SNOMED CT
SNOMED CT (Systematized Nomenclature of Medicine--Clinical Terms) is a comprehensive clinical terminology, originally created by the College of American Pathologists (CAP) and, as of April 2007, owned, maintained, and distributed by the International Health Terminology Standards Development Organisation (IHTSDO), a not-for-profit association in Denmark. The CAP continues to support SNOMED CT operations under contract to the IHTSDO and provides SNOMED-related products and services as a licensee of the terminology.
T
Technical Specification
See HSPC Technical Specification.