Glossary of Terms

[ 1 A ] [ 2 B ] [ 3 C ] [ 4 D ] [ 5 E ] [ 6 F ] [ 7 G ] [ 8 H ] [ 9 I ] [ 10 J ] [ 11 K ] [ 12 L ] [ 13 M ] [ 14 N ] [ 15 O ] [ 16 P ] [ 17 Q ] [ 18 R ] [ 19 S ] [ 20 T ] [ 21 U ] [ 22 V ] [ 23 W ] [ 24 X ] [ 25 Y ] [ 26 Z ]

A

B

C

Codebase

The Logica Reference Implementation and all of the Logica 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 Logica 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 Logica 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. Logica strives to be compatible with the current release version of FHIR.

Logica Ecosystem

The Logica Ecosystem is composed of the project initiatives, software systems, industry specifications, galleries, reference implications, and applications for the consortium.

Logica FHIR Profiles

Logica is actively producing a large set of FHIR Profiles. You can find more details in the Modeling and Terminology Initiatives project space.

Logica Java Client Library

The Logica Java Client Library is an open source implementation of the SMART on FHIR client specification.

Logica Patient Data Manager

The Logica 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.

Logica Reference Implementation

The Logica Reference Implementation is an implementation of the Logica Technical Specification (including SMART on FHIR and FHIR DSTU2).

Logica Sandbox

The Logica Sandbox is a site where users can create sandbox instances. A sandbox instance is a personal instance of the Logica Technology Stack including the Logica Reference Implementation, a FHIR database, and a registry for the user's apps.

Logica Technical Specification

The Logica Technical Specification describes the platform, technologies, and tiers of the Logica ecosystem.

Logica Technology Stack

The Logica Technology Stack is an open-source implementation of the Logica Technical Specification. The Logica Technology Stack includes the Logica Reference Implementation, the Logica Sandbox, and the Logica Tools Suite.

Logica Tools Suite

The Logica Tools Suite consists of the tools created by Logica Development for the purpose of enabling the creation, testing, and marketing of SMART on FHIR apps. Tools include the Logica 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. Logica uses HTTP/HTTPS as the transport protocol for communication between apps, resource servers, and authorization servers.

I

J

Java Client Library

See Logica 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 Logica 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 Logica 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 Logica Technical Specification uses OpenID Connect for identity.

P

Q

R

Reference Implementation