№09 · Reference

Healthcare technology glossary.

The Yellowcross glossary defines the operational, technology, regulatory, and business terms that shape telemedicine, teleradiology, imaging, and healthcare practice management. Where useful, each entry links to the Yellowcross service area where it most commonly appears.

Section imaging

Imaging & radiology

Systems and standards that govern how radiology images are produced, stored, displayed, and read.

01 PACS Picture Archiving and Communication System

A PACS is the medical imaging system that stores, retrieves, and displays radiology images — CT, MRI, X-ray, ultrasound, mammography — for radiologists and referring clinicians.

Most modern PACS platforms integrate with a RIS for workflow management and use DICOM as the underlying image data standard. PACS selection drives almost every other technology decision in a radiology practice, which is why Yellowcross treats it as the foundation of any technology integration engagement.

See also: RIS DICOM Technology integration

02 RIS Radiology Information System

A RIS is the operational software that manages a radiology practice's workflow: patient scheduling, exam ordering, technologist worklists, dictation routing, billing, and reporting.

A RIS sits between the EHR and the PACS — it tracks the case through every step from order to finalized report. Integration quality between RIS, PACS, and EHR is the single most common source of "the system doesn't work" complaints in radiology operations.

See also: PACS EHR

03 DICOM Digital Imaging and Communications in Medicine

DICOM is the international standard that defines how medical imaging data is formatted, stored, and transmitted between devices and systems.

Every modern imaging modality (CT scanner, MRI, X-ray, ultrasound) emits DICOM-formatted studies, and every PACS speaks DICOM natively. DICOM compliance is a baseline check during vendor evaluation — but DICOM conformance statements vary enormously and real-world interoperability requires careful testing.

04 Voice recognition / dictation

Voice recognition (VR) is the technology radiologists use to dictate reports directly into the RIS or PACS report module, replacing the older workflow of dictating to a tape and waiting for transcription.

Modern radiology VR systems (Nuance PowerScribe, etc.) achieve high accuracy on radiology-specific vocabulary and templated reports. Practices that skip VR optimization often see report turnaround times stretch by hours per case — a workflow bottleneck Yellowcross specifically addresses during practice management engagements.

05 AI / CAD Artificial Intelligence / Computer-Aided Detection

AI and CAD tools assist radiologists by automatically detecting findings (nodules, fractures, hemorrhages) or triaging studies by suspicion of critical findings.

AI tools used in clinical diagnosis are regulated as Software as a Medical Device (SaMD) by the FDA. Academic studies show 451–791% five-year ROI on properly integrated AI in some radiology contexts, but integration with PACS workflow is where most deployments succeed or fail.

See also: FDA SaMD

Section records

Records & interoperability

Standards for how clinical and administrative data is structured and exchanged between systems.

06 EHR Electronic Health Record

An EHR is the comprehensive, longitudinal record of a patient's clinical care across providers and specialties, intended to be shareable between healthcare organizations.

EHR is the broader, modern term; "EMR" is sometimes used interchangeably but technically refers to records confined within a single practice. Major EHR vendors include Epic, Cerner, Athenahealth, and eClinicalWorks; each has distinct integration patterns with imaging, billing, and telemedicine platforms.

See also: EMR FHIR

07 EMR Electronic Medical Record

An EMR is the digital version of a single practice's paper chart — a record of a patient's care within one healthcare organization.

The distinction between EMR and EHR matters less in practice than in the literature; many vendors use the terms interchangeably. The substantive question is whether the system supports interoperability standards (HL7, FHIR) for exchanging records with outside providers and specialty systems.

08 HL7 v2 Health Level Seven International, version 2

HL7 v2 is the older but still widely deployed messaging standard for exchanging clinical and administrative data between healthcare applications — orders, results, admissions, billing.

Almost every healthcare integration project in operation today involves HL7 v2 interfaces. New integrations should generally be built FHIR-first, but most existing systems will continue to communicate via HL7 v2 for years to come.

See also: FHIR

09 FHIR Fast Healthcare Interoperability Resources

FHIR is the modern healthcare data exchange standard, built on web APIs (REST, JSON) and designed to replace or supplement HL7 v2 and CDA for next-generation interoperability.

FHIR adoption is now mandated for certified EHRs under the 21st Century Cures Act. If you're selecting new healthcare systems in 2026 and beyond, FHIR-capability is non-negotiable; existing HL7 v2 integrations don't need to be ripped out but new ones should be designed FHIR-first.

See also: Technology integration

Section compliance

Compliance & regulation

The federal and contractual frameworks that govern how healthcare data is protected and how clinical software is regulated.

10 HIPAA Health Insurance Portability and Accountability Act

HIPAA is the 1996 federal law that establishes national standards for the protection of patient health information (PHI), with both Privacy and Security rules that govern healthcare providers, plans, and their vendors.

Every system that touches PHI must meet HIPAA technical, administrative, and physical safeguards. Vendor relationships involving PHI require a Business Associate Agreement (BAA). HIPAA violations carry per-incident penalties that can reach into the millions for repeat or willful non-compliance.

See also: BAA PHI

11 HITECH Health Information Technology for Economic and Clinical Health Act

HITECH is the 2009 law that expanded HIPAA enforcement, mandated breach notification, and incentivized EHR adoption through the Meaningful Use program.

HITECH significantly raised the financial and reputational stakes of HIPAA non-compliance, particularly around breach notification. Any technology integration project that touches PHI must consider HITECH breach-notification protocols alongside HIPAA technical safeguards.

12 BAA Business Associate Agreement

A BAA is a federally required contract between a HIPAA-covered entity (a practice) and any third-party vendor that handles PHI on its behalf — cloud providers, billing services, telemedicine platforms, AI tools.

No vendor should touch PHI without a signed BAA. Vendor due diligence during integration projects always includes BAA review; some vendors decline to sign one, which is usually a disqualifier for healthcare deployment.

13 PHI Protected Health Information

PHI is any individually identifiable health information held or transmitted by a covered entity or its business associate — names tied to diagnoses, images, billing records, etc.

PHI is the operative term in HIPAA. De-identified data (per the Safe Harbor or Expert Determination methods) is not PHI and is not subject to HIPAA, but the de-identification standards are strict.

14 FDA SaMD Software as a Medical Device

SaMD is the FDA's regulatory category for software that performs medical functions independent of a hardware device — including most AI diagnostic tools used in radiology, cardiology, and other specialties.

Any AI tool that influences clinical decisions typically requires FDA clearance (510(k) or De Novo) before US deployment. Yellowcross vets FDA status as part of vendor evaluation for AI integration projects.

See also: AI / CAD

Section licensing

Licensing & credentialing

The workforce-side of healthcare regulation — who is allowed to practice where, and how that is documented.

15 IMLC Interstate Medical Licensure Compact

The IMLC is an agreement among 41+ US states, DC, and Guam that streamlines the process for physicians to obtain medical licenses in multiple member states.

For telemedicine practices that treat patients across state lines, the IMLC dramatically reduces the time and paperwork required to get licensed in new states — often weeks rather than months per state. Yellowcross builds an IMLC roadmap as part of the planning phase of telemedicine engagements.

See also: Telemedicine consulting

16 NPI National Provider Identifier

An NPI is a 10-digit federal identifier required for every individual healthcare provider and organization that bills US payers.

NPIs are issued by CMS through NPPES and are used in essentially every healthcare administrative transaction — claims submission, prescribing, EHR provenance. Practices manage both individual (Type 1) NPIs and group/organization (Type 2) NPIs.

See also: CMS

17 Board certification

Board certification is voluntary certification by a specialty board (e.g., the American Board of Radiology) verifying that a physician has met the training and examination standards of their specialty beyond basic medical licensure.

Most teleradiology positions — including Yellowcross radiologist openings — require board certification (or board eligibility) plus relevant subspecialty fellowship training for neuroradiology, MSK, body imaging, etc.

18 Multi-state licensure

Multi-state licensure refers to a physician holding active medical licenses in more than one state — required when treating patients in any state where the physician is not already licensed.

The state in which the patient is located at the time of the visit (not the physician's location) determines which medical license applies. The IMLC and state-specific telemedicine licenses both reduce friction, but the underlying rule still requires careful licensing maps for any practice operating across state lines.

See also: IMLC

Section billing

Billing & revenue cycle

The financial machinery of healthcare practices — how care turns into reimbursable claims and ultimately into revenue.

19 RCM Revenue Cycle Management

RCM is the financial process that tracks patient encounters from registration and insurance verification through billing, claims submission, payment posting, and follow-up on denials.

Many practices outsource RCM to specialized vendors. Well-run RCM can compress days-to-payment by 20–30% and improve collection rates by 15–25% over poorly managed in-house billing. Yellowcross practice management engagements include RCM evaluation and vendor coordination.

See also: Practice management

20 CPT Current Procedural Terminology

CPT codes are the five-digit codes (maintained by the AMA) that physicians use to identify the medical, surgical, and diagnostic services they perform on a claim.

Accurate CPT coding is foundational to revenue cycle performance — undercoding leaves money on the table, overcoding triggers audits and clawbacks. Telemedicine has its own family of CPT modifiers (95, GT, etc.) that determine reimbursement.

21 ICD-10 International Classification of Diseases, 10th Revision

ICD-10 is the international diagnostic coding system used in the US (as ICD-10-CM for diagnoses) to indicate the medical reason for a service rendered.

CPT codes describe the procedure performed; ICD-10 codes describe the diagnosis or reason for the procedure. Both are required on most claims, and payers use the pairing to determine medical necessity and reimbursement.

22 CMS Centers for Medicare & Medicaid Services

CMS is the US federal agency that administers Medicare, Medicaid, and CHIP, and sets the reimbursement rules that drive much of the rest of the US payer landscape.

CMS rate decisions cascade through commercial payer contracts. CMS also runs the NPI registry and the Quality Payment Program. Practice management engagements often involve modeling the impact of CMS rule changes on a practice's revenue mix.

Section telemedicine

Telemedicine & remote care

The vocabulary of remote care delivery — the disciplines, workflows, and shift patterns that distinguish telemedicine and teleradiology from in-person practice.

23 Telemedicine

Telemedicine is the delivery of clinical care to patients who are not physically present with the provider, using video, phone, asynchronous messaging, or remote monitoring.

Telemedicine encompasses virtual visits across most specialties — primary care, behavioral health, dermatology, cardiology, radiology, and more. Implementation success depends as much on workflow design and change management as on platform selection.

See also: Telemedicine consulting

24 Teleradiology

Teleradiology is the subset of telemedicine in which radiologists interpret medical images (CT, MRI, X-ray, ultrasound) remotely — often for hospitals, imaging centers, or other practices located elsewhere.

Teleradiology is the most mature and profitable segment of telemedicine, valued at $12.6–15.6B as of 2023–2024 with projected 15–26% CAGR through 2032. Yellowcross specializes in teleradiology operations and recruits board-certified radiologists for daycall, nightcall, and final-read coverage.

See also: Daycall Nightcall Final read Radjobs

25 Daycall

Daycall is teleradiology coverage during standard business hours (typically 8am–5pm local time) — usually first-read interpretation for routine imaging studies.

Daycall is the volume backbone of most teleradiology practices. Coverage patterns vary by client: some need full-shift weekday coverage, others use teleradiologists as overflow for specific subspecialties.

26 Nightcall

Nightcall is teleradiology coverage during overnight hours — typically the most acute studies (ER, trauma) requiring rapid interpretation.

Nightcall is often delivered as a "preliminary read" (or "wet read") to the on-call clinician, with a final read issued the following morning by the on-site or daycall radiologist. Premium reimbursement reflects the acuity and inconvenient hours.

See also: Wet read Final read

27 Wet read / preliminary read

A wet read is an initial radiology interpretation issued quickly — often by an on-call or nightcall radiologist — to guide immediate clinical decisions, pending a more comprehensive final read.

The term "wet read" originates from film-era radiology, when films were physically still wet from chemical processing when the first read was given. Today wet reads coexist with final reads in most teleradiology workflows and discrepancies between the two are tracked as a quality metric.

28 Final read

A final read is the comprehensive, signed-off radiology report that becomes the official interpretation of a study and the document used for billing.

Final-read responsibility typically rests with the day-shift or in-house radiologist when a wet read was delivered overnight. Final-read radiologists are also accountable for any over-reads or discrepancy reviews of earlier preliminary interpretations.

29 Tele-stroke

Tele-stroke is a specialty telemedicine subsegment in which a remote neurologist evaluates stroke patients (typically in an emergency department) within the narrow time window required for thrombolytic intervention.

Tele-stroke programs are common in rural and community hospitals that lack on-site neurology coverage. Successful tele-stroke implementation requires tight integration between the hospital EHR, the imaging chain (CT/MR), and the remote neurologist's workflow.

30 Tele-ICU

Tele-ICU is a telemedicine model in which a remote critical-care team (intensivists, ICU nurses) monitors and co-manages ICU patients via continuous audiovisual and physiologic data feeds.

Tele-ICU is associated with reduced ICU mortality and shorter stays in published studies. Implementation involves significant integration work between the bedside hospital monitoring systems and the remote command center.

Section engagement

Engagement & operations

How consulting and management engagements are structured — the vocabulary clients use when buying services from Yellowcross or similar firms.

31 Fee-for-service consulting

Fee-for-service consulting is an engagement model in which the consultant is paid for a defined scope of work with specific deliverables, rather than on retainer or contingency.

Yellowcross operates exclusively on a fee-for-service basis — each engagement has agreed deliverables, timeline, and fee. Clients can end engagements when deliverables are met, with no long retainers or vendor commissions creating misaligned incentives.

See also: Practice management

32 Complete practice management

Complete practice management is an engagement in which a firm runs the operational layer of a practice end-to-end — operations, IT, billing, HR, business development, branding.

Complete management is structured annually with quarterly reviews and a 60-day exit clause on either side. Best for practices that need an operational infrastructure built and run, not just advised.

See also: Fractional management Consultative engagement

33 Fractional management

Fractional management is an engagement in which a firm manages specific operational functions part-time — typically operations, IT, billing/RCM, HR, or business development — alongside the practice's in-house team.

Fractional engagements run monthly with a typical commitment of 6–12 months. Best for practices that have most functions in place but are missing one or two — a CFO-equivalent for billing, for example, without the full executive cost.

34 Consultative engagement

A consultative engagement is an advisory-only relationship in which the firm produces assessments, recommendations, and roadmaps but does not take operational control.

Consultative engagements run 4–12 weeks and produce written deliverables: assessments, technology selection memos, implementation roadmaps. Best for practices that need direction and expertise, not staffing.

35 Change management

Change management is the discipline of guiding staff and clinicians through operational transitions — new technology, new workflows, new policies — so adoption actually happens.

In healthcare IT specifically, Black Book Research found that 100% of healthcare professionals surveyed experienced workflow disruptions from major IT implementations, with 77% reporting ongoing workflow issues. Change management is the single biggest predictor of whether an implementation succeeds or stalls.

Missing a term?

Tell us what to add.

Yellowcross expands this glossary based on what clients actually ask about. If you'd like a term defined, let us know.

Suggest a term