42 CFR Part 2
42 CFR Part 2 (commonly referred to as "Part 2") are the
federal regulations governing
the confidentiality of drug and alcohol abuse treatment and prevention records
C32
A C32 is a type of Continuity of Care Document (CCD) which
focuses on the patient's summary information. The data is extracted from RPMS. The
demographic data and patient identity are confirmed through the MPI. Then the C32
document is put into the Registry and Repository.
C-CDA
Consolidated Clinical Document Architecture (C-CDA) is a complete architecture used to create documents and template methodologies for those documents. The primary function of the C-CDA is to standardize the content and structure for clinical care summaries. Templates are set at three levels – Document level, Section level and Entry level.
Consent Mgmt.
A module used to create and manage consent policies that
determine the level of privacy applied to the patient’s health record when it is shared
between providers and/or patients and providers
CTX API
The Context Handler (CTX) API makes decisions based on the
consent policy
Direct
A standards-based system component used for secure email
communication and transactions between providers, patients and health care organizations
Docker
An open-source program that enables a Linux application and its
dependencies to be packaged as a container
DSS API
The Data Segmentation Service (DSS) API handles the segmentation
of a patient’s sensitive health information per their consent. BRMS service is included in
DSS
EHR
The system component that providers use to manage a patient’s
health records and where patient health data will originate
FHIR
Fast Healthcare Interoperability Resources (FHIR) and pronounced
as "Fire,” defines a set of "Resources" that represent granular clinical concepts. The
Resources can be managed in isolation, or aggregated into complex documents. Technically,
FHIR is designed for the web. The Resources are based on simple XML or JSON structures, with
an http-based RESTful protocol where each Resource has predictable URL. Where possible, open
internet standards are used for data representation.
HIE
The system components where the patient health information
originates, and which integrates with the IExHub and Patient Portal
HL7
Health Level-7 or HL7 refers to a set of international standards
for the transfer of clinical and administrative data between software applications used by
various healthcare providers. These standards focus on the application layer, which is
"layer 7" in the OSI model.
IExHub
A component that provides the Consent2Share application with
common semantic process and interoperability capabilities to enable access to patient health
data via a standards based
HIE implementations
Java
A general-purpose computer programming language designed to
produce programs that will run on any computer system
Java Script
An object-oriented computer programming language commonly used
to create interactive effects within web browsers
MPI
A master patient index (MPI) is an electronic medical database
that holds information on every patient registered at a healthcare organization.
NPI
A national provider identifier (NPI) is a unique 10-digit
identification number required by HIPAA for all health care providers in the United States.
Providers must use their NPI to identify themselves in all HIPAA transactions.
PAT API
The Patient User Setup (PAT) API links a "Patient" record (e.g.
patient, self, or guardian) to a standard user account and allows the UAA to associate it
with a user functions template
Patient Data Entry
A module used for patient self-managed health data, track
fitness and health progress, and collect medical readings from electronic medical devices
Patient Identity Mgmt.
A module used to create and manage patient records in the HIE
Patient Management
A module used by administrative staff to create and manage
patient account
Patient UI
An application component that is used by the patient to manage
his/her health information
PCM API
The Patient Consent Management (PCM) API handles the creation
and editing of consent. It also provides the policy for segmentation
PDQ
The PIX/PDQ Manager forms a specialized implementation of HL7
messaging that facilitates patient health information exchange, and supports both HL7 v2 and
HL7 v3 messaging
PEP API
The Policy Enforcement Point (PEP) API receives requests for
patient information and records and checks to see how to handle the request
PHI
Protected Health Information (PHI) is any information about health status, provision of health care, or payment for health care that can be linked to a specific individual. Under HIPAA, PHI includes such items as names, phone numbers, email addresses, social security numbers, medical record numbers, and more.
PHR API
The Patient Health Record (PHR) API handles requests for viewing
and sharing patient health information, and patient entered data
PHR CACHE
Temporarily stores patient health information retrieved from the
IExHub
PIX
The PIX/PDQ Manager forms a specialized implementation of HL7
messaging that facilitates patient health information exchange, and supports both HL7 v2 and
HL7 v3 messaging
PLS API
The Provider Lookup Service (PLS) API handles requests such as
when a user searches for a provider
Provider Mgmt.
A module to search and manage the patient’s providers
REG API
The Patient Registration (REG) API handles patient account
creation and requests
Secure Token Service
Federated security model that controls access across several
modules and services by issuing tokens for authentication and authorization
Share PHI
A module that uses consents to share patient health information
between providers and/or patients and providers
SQL
Structured Query Language (SQL) is a standard computer language
for relational database management and data manipulation. SQL is used to query, insert,
update and modify data.
Staff Account Management
A module used by power user (administrative staff) to create and
manage user accounts
Terminology Service
A standards-based third-party service used to manage coded
concepts via SOAP/REST
TRY API
The Try My Policy (TRY) API allows patients to try-their-policy
against their medical record or a sample medical record in order to view the segmented
medical record
User Management
A module used by administrative staff to create and manage user
accounts.
VAL API
The Document Validator (VAL) API validates C-CDA R1 and 2.1
documents based on schema and schematron rules
Value Set Management
A module used by administrative staff to manage value sets and
map them to appropriate sensitivity categories and privacy settings
VSS API
The Value Set Service (VSS) API handles the creation and editing
of value sets with the potential to use external services, such as VSAC
VSS CACHE
Temporarily stores value set information in cache memory
XDS.b
Cross-Enterprise Document Sharing XDS.b is a Microsoft Connected
Health Platform Solution Accelerator based on the IHE (www.ihe.net) XDS.b integration
profile. XDS.b facilitates the registration, distribution, and access across health
enterprises of patient electronic information in document format.