Healthcare software glossary
The terms that come up when you buy, build or integrate healthcare software, each defined in a sentence or two, with the detail and the sources behind it.
B
- BAA · Business Associate Agreement
A Business Associate Agreement (BAA) is the contract HIPAA requires before a covered entity lets a vendor create, receive, maintain, or transmit protected health information on its behalf. It limits what the vendor may do with the data, requires safeguards and breach reporting, and says what happens to the data when the contract ends.
C
- CCM · Chronic care management
Chronic care management (CCM) is a Medicare-paid, mostly non-face-to-face service for patients with two or more chronic conditions that are expected to last at least 12 months, or until death, and that put them at significant risk of death, acute exacerbation or decompensation, or functional decline. Practices bill it monthly based on time spent coordinating the patient's care. - CDS Hooks · Clinical Decision Support Hooks
CDS Hooks is an HL7 specification that lets an EHR call an outside decision support service at set moments in a clinician's workflow, such as opening a chart or signing an order, and show the reply as cards inside the EHR. The service is expected to answer in about half a second.
E
- EHR · Electronic health record
An EHR is a digital version of a patient's chart, kept by health care providers over time, that holds demographics, diagnoses, medications, notes, test results and billing details and is designed to be shared across care settings. The term also names the software system that hospitals and practices use to keep those records. - EMR · Electronic medical record
An EMR is a digital version of the paper chart in one clinician's office or practice, holding the medical and treatment history of that practice's patients. ONC distinguishes it from an EHR, which is built to share information across providers and care settings. - EVV · Electronic visit verification
Electronic visit verification (EVV) is a system that electronically verifies in-home visits for Medicaid personal care and home health services, recording the type of service, who received it, the date, the location, who provided it, and when it started and ended. Section 12006 of the 21st Century Cures Act requires states to use it.
F
- FDA 510(k) · Premarket notification
A 510(k) is a premarket notification to FDA showing that a device is substantially equivalent to a legally marketed predicate device: it has the same intended use, and either the same technological characteristics or different ones that do not raise different questions of safety and effectiveness. The device cannot be marketed until FDA issues an order finding it substantially equivalent. - FHIR · Fast Healthcare Interoperability Resources
FHIR is the HL7 standard for exchanging healthcare information electronically, built from modular data units called resources (Patient, Observation, Encounter and so on) that can be read and written over a web API in JSON or XML. It is the standard US certification rules require EHRs to use for their patient and population data APIs.
H
- Healthcare interoperability
Healthcare interoperability is the ability of health IT systems to exchange electronic health information and use it without special effort on the part of the user, as the 21st Century Cures Act defines it. In practice it means records move between EHRs, apps, payers and networks in standard formats and arrive in a form the receiving system can act on. - HIPAA Privacy Rule
The HIPAA Privacy Rule sets the national standards for when covered entities and business associates may use and disclose protected health information, and gives patients rights over their own records, including the right to get a copy. It applies to PHI in any form, not only electronic data. - HIPAA Security Rule
The HIPAA Security Rule requires covered entities and business associates to ensure the confidentiality, integrity, and availability of the electronic protected health information they create, receive, maintain, or transmit. It does this through administrative, physical, and technical safeguards set out in 45 CFR Part 164, Subpart C. - HL7 v2 · Health Level Seven Version 2 messaging standard
HL7 v2 is the older HL7 messaging standard in which systems send event-driven messages made of reusable segments, such as an admission or a lab result. HL7 calls it one of its most widely adopted standards, prominent in inpatient settings around the world.
I
- IEC 62304 · Medical device software: Software life cycle processes
IEC 62304 is the international standard that defines life cycle requirements for medical device software, for both development and maintenance, whether the software is itself a medical device or part of one. FDA accepts a declaration of conformity to its FDA-recognized version as evidence of software development and maintenance practices in a premarket submission. - Information blocking
Information blocking is a practice by a health care provider, a developer of certified health IT, or a health information network that is likely to interfere with access, exchange or use of electronic health information, unless it is required by law or fits a regulatory exception. The 21st Century Cures Act prohibits it, and HHS enforces it with penalties of up to $1 million per violation for developers and networks. - ISO 14971 · Medical devices: Application of risk management to medical devices
ISO 14971 is the international standard for risk management of medical devices, including software as a medical device. It sets the process for identifying hazards, estimating and evaluating the associated risks, controlling them, and monitoring whether the controls work.
M
- Minimum necessary standard
The HIPAA minimum necessary standard requires covered entities and business associates to make reasonable efforts to limit protected health information to the minimum needed for the purpose of a use, disclosure, or request. It does not apply to disclosures to a provider for treatment, disclosures to the patient, or disclosures under the patient's authorization, among other exceptions.
O
- ONC Health IT Certification · ONC Health IT Certification Program
ONC Health IT Certification is a voluntary federal program, run by ASTP/ONC with third-party certification bodies, that tests health IT such as EHRs against criteria set by HHS. It matters because CMS programs and other rules require providers to use certified health IT.
P
- Patient portal
A patient portal is a secure website or app, offered by a provider or health system, that gives patients 24-hour access to their health information, such as lab results and medications, and often lets them message clinicians, book appointments, request refills and pay bills. In 2024, 77% of US individuals were offered online access to their records. - PCCP · Predetermined change control plan
A predetermined change control plan (PCCP) is a section of a device's marketing submission that describes planned modifications, the methods for developing, validating, and implementing them, and an assessment of their impact. Once FDA authorizes the plan, changes made consistent with it do not need a new 510(k) or PMA supplement. - PHI · Protected health information
Protected health information (PHI) is individually identifiable health information that a HIPAA covered entity or business associate holds or transmits, in electronic, paper, or any other form. It covers information about a person's health, care, or payment for care that identifies them or could reasonably be used to identify them.
Q
- QHIN · Qualified Health Information Network
A QHIN is a health information network designated by the TEFCA Recognized Coordinating Entity to act as a central connection point for nationwide exchange. Providers, payers and apps join TEFCA by connecting through a QHIN, not directly.
R
- RPM · Remote patient monitoring
Remote patient monitoring (RPM), which Medicare bills as remote physiologic monitoring, uses a connected medical device to collect a patient's physiologic data, such as blood pressure, oxygen saturation, blood sugar, or weight, and transmit it automatically to a practitioner who uses it to manage an acute or chronic condition. - RTM · Remote therapeutic monitoring
Remote therapeutic monitoring (RTM) is a Medicare-covered service that uses a connected medical device to collect non-physiological data related to a therapeutic treatment, such as musculoskeletal or respiratory status, treatment adherence, and treatment response. Unlike remote physiologic monitoring, the data can be self-reported by the patient.
S
- SaMD · Software as a Medical Device
Software as a Medical Device (SaMD) is software intended for one or more medical purposes that performs those purposes without being part of a hardware medical device. FDA uses this definition from the International Medical Device Regulators Forum (IMDRF). - SBOM · Software bill of materials
A software bill of materials (SBOM) is a nested inventory of the components that make up a piece of software, a list of its ingredients. For medical devices, section 524B of the FD&C Act requires sponsors of cyber devices to provide one in premarket submissions, covering commercial, open-source, and off-the-shelf components. - SMART on FHIR · SMART App Launch Framework
SMART on FHIR is the HL7 specification, based on OAuth 2.0, that lets an app sign in against an EHR, get the user's permission, and read FHIR data, either launched from inside the EHR or standalone. US-certified EHRs must support it for their patient and clinician APIs.
T
- TEFCA · Trusted Exchange Framework and Common Agreement
TEFCA is the US nationwide framework for exchanging health records between networks: a set of shared principles plus a legal contract, the Common Agreement, signed by designated networks called QHINs. Exchange under TEFCA began in December 2023. - Telehealth
Telehealth is the delivery of health care services through two-way interactive communication technology, usually live video and in some cases audio only, as a substitute for an in-person visit. In Medicare it is a defined benefit with its own list of covered services and rules on technology and patient location.
U
- US Core · HL7 FHIR US Core Implementation Guide
US Core is the HL7 implementation guide that defines the minimum rules a FHIR R4 server in the US must follow for each kind of patient data, such as which fields must be present and which code systems to use. It is how USCDI becomes concrete FHIR, and certified EHR APIs must conform to it. - USCDI · United States Core Data for Interoperability
USCDI is the federal list of health data elements, grouped into data classes, that certified health IT in the US must be able to exchange. ASTP/ONC publishes a new version every year, and USCDI v3 became the certification baseline on January 1, 2026.