website logo
⌘K
👋Welcome!
🚀About Founda
Introduction to Founda
Glossary
🔌Getting started
Start your integration
Founda FHIR Sandbox
🧑‍🏫Tutorials
Console
Authentication with OAuth2.0
📖Interaction Guides
Patient Demographics Exchange
Clinical Information Exchange
Subscription Management
Audit Record Repository
Docs powered by archbee 
website logo
1min

Glossary

An overview of all the Founda definitions and their meaning.

Term

Meaning

API Gateway

The main API of Founda. The way Applications connect to Founda, and get access to the Providers Founda has connected to.

Application Provider

Provides one or more applications considered "external" or "third party" to the Provider Organization that act upon or create patient health data from/for a Provider Organization.

Application

The application/solution that uses Founda’s gateway to integrate with healthcare organizations.

Client

A party that consumes data from a data source from a healthcare provider. A Client has a n to n relation with organizations. Each Client is configured with a set of permissions of data they can send or receive from Providers. A Provider must approve a Client before it works for that Provider.

Console

The web-app where administrators can configure users, API clients and other settings related to their connections and integrations.

FHIR

Fast Healthcare Interoperability Resources, an information standard describing minimally relevant clinical concepts and its data structure, for use in exchanging information using an application programming interface.

IHE

Integrating the Healthcare Enterprise is a collaboration by healthcare professionals and industry that promotes the use of standards to address specific clinical needs. IHE Domains develop and maintain integration profiles for healthcare domains.

Organization

A technical term that encompasses all organizations on the Founda platform. It also includes the root organization “Founda” (administrative organization).

Patient Identifier Domain

A single system or a set of interconnected systems that all share a common identification scheme (an identifier and an assignment process to a patient) and issuing authority for patient identifiers.

Provider Organization

Represents an organization that maintains patient health information and that has a need to share this information with others.

Resource Action(s) (FHIR)

An Operation that can be performed onto an API resource, in this case a FHIR resource. Resource actions are to be understood as HTML methods for RESTful services

Sandbox (Provider)

An organization acting as a Provider Organization an application can interact with. The current sandboxes contain FHIR resources. An Application Provider can make test calls through our Health API to this Provider Organization.

Scope (FHIR)

The combination of a FHIR Resources (.e.g. Patient or Observation) and the Restful actions (Create, Update, Read, Delete, etc.) are referred to as a "scope". Application Providers must define the scopes their application(s) require in order to function. Provider organizations accept or reject the requested scopes.

Source System

A (clinical information) system of the Provider Organization.

Subscription

A Subscription can be configured by an Application Provider to receive all messages from the Provider Organization that meet certain conditions.

Subscription Topic

Provider Organizations can create Subscription Topics to filter all the messages that are sent based on a specific activity, which require a specific action from an Application Provider.

Trigger event

A message that describes an event taking place, for example a patient being admitted to the hospital. Commonly communicated using HL7v2 messages.

Transformation

Changing a data as it is stored in one format and standard, to another format and/or standard that retains the exact same semantic value (in a clinical context); aka “mapping”.



Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
Start your integration
Docs powered by archbee