Vital Signs

An enterprise master patient index (EMPI) is a system that maintains consistent, accurate information about each registered patient and can link smaller patient indexes or aggregate data across systems. This post explains deterministic, probabilistic, and referential matching, what an evaluation against a 30,000-record gold standard from a health information exchange with over 47 million registrations found, and what a linkage study of 2,247 patients shows about method choice.

Integration is the process of joining separately developed parts so they function as one connected system. This post explains the common approaches in health IT, from point-to-point interfaces and interface engines to APIs and single-platform strategies, and what a focus group study, a sepsis transitions study with 91 participants, and a 13-year Scottish case study found about missing data and long-term integration efforts.

A Continuity of Care Document (CCD) is an XML patient summary built on the HL7 Clinical Document Architecture that lets systems exchange a standard set of clinical sections such as problems, medications, allergies, and vital signs. This post explains how the CCD relates to the broader C-CDA standard, which versions federal rules reference, and what studies of real exchanged documents found about conformance, completeness, and agreement between networks.

A FHIR resource is the basic building block of the HL7 FHIR standard: all exchangeable content is defined as a resource with a common way of representing data, shared metadata, and a human-readable part. This post explains what every resource contains, how profiles and implementation guides narrow them, and what recent reviews found about FHIR mapping quality, machine learning systems, and a national reporting system.

A code set is a set of elements mapped to another set according to a coding scheme. Clinical code sets identify conditions, procedures, services, equipment, and supplies, while administrative code sets characterize entities and events for administrative processes. This post covers the medical code sets HIPAA adopted, a German study of sepsis coding accuracy, and a randomized experiment on map-assisted ICD-10-CM coding.

A sensitivity label is a security level associated with the content of information, marking data that carries a heightened potential for harm to the patient or others. This post explains how labels work in HL7 FHIR, why they depend on policy and trust to mean anything, and what research on granular consent and pediatric data sharing says about the challenges.

The Interoperability Standards Advisory, or ISA, is the process and online resource through which the Office of the National Coordinator for Health Information Technology identifies and publicizes interoperability standards and implementation specifications for specific needs. This post explains how the ISA is organized, what adoption levels mean, how Reference Editions work, and what a listing does not require.

Structural interoperability is the shared structure and format of data exchange, the message standards that let a receiving system read data at the field level. This post explains how it differs from foundational and semantic levels, how HL7 v2 and FHIR define structure and validation, what recent studies show about pairing structure with meaning, and where nurses and informaticists see structure problems.

MeSH, the Medical Subject Headings thesaurus, is the National Library of Medicine’s controlled, hierarchical vocabulary for indexing, cataloging, and searching biomedical information. This post explains its descriptors and tree structure, how automated indexing with the Medical Text Indexer works and where humans still step in, and how nurses and informaticists can use MeSH for better evidence searches.

Foundational interoperability is the first level of interoperability: the building blocks that let one system connect to another to send and receive data. This post explains how it differs from structural and semantic levels, what a scoping review of EHR interoperability found, what ONC reports on national exchange, and why connection alone does not mean usable data.

Electronic prior authorization, or ePA, uses the NCPDP SCRIPT standard to let a prescriber submit medication-specific prior authorization criteria and receive an approval in real time. This post explains how ePA works, how it differs from the CMS prior authorization API rule that excludes drugs, what a survey of 8,419 family physicians found about administrative burden, and how nurses and staff are affected.

MedDRA is the international medical terminology used by regulators and manufacturers to document, report, and monitor the safety of medical products. This post explains its hierarchy, how the FDA’s adverse event reporting system uses it, what a registry study that coded post-vaccination symptoms with MedDRA shows, and where clinicians and informaticists encounter it.

XML, the Extensible Markup Language, is a W3C specification that lets designers create their own tags to describe data so that different systems can share it. This post explains elements, attributes, and schemas, where XML appears in CDA, FHIR, and CDISC standards, how it compares with JSON, and why secure parsing matters.

The HL7 Clinical Document Architecture, or CDA, is an XML-based standard for the structure and semantics of clinical documents so they can be exchanged and read by both machines and people. This post explains the six characteristics of a clinical document, how CDA relates to C-CDA and FHIR, what research found about real-world document quality, and why nurses and informaticists should care.

ASC X12 is the ANSI-accredited standards body that develops the electronic data interchange transaction sets used in health care claims, eligibility, claim status, referral authorization, enrollment, and payment. This post explains how X12 transactions are structured, which ones HIPAA adopted, what version 5010 and operating rules add, and how clinical documentation and registration connect to these files.

An infobutton is a link inside the EHR that sends the clinical context, such as the medication, diagnosis, patient age, or user role, to a knowledge resource so the response fits the situation. This post explains the HL7 Context-Aware Knowledge Retrieval standard, how requests and responses work, what a systematic review found about infobutton design, and how nurses and informaticists can use infobuttons for evidence and patient education.

Cross-Enterprise Document Sharing, or XDS, is an Integrating the Healthcare Enterprise profile for registering, locating, and retrieving clinical documents across organizations. This post explains the registry and repository model, what an affinity domain is, what XDS does not do, and what recent studies say about technical implementation and governance.

A healthcare clearinghouse converts health information between nonstandard formats and the standard transactions HIPAA requires, and the regulation treats it as a covered entity. This post explains the regulatory definition, the transactions involved, how clearinghouses differ from payers and vendors, and what the 2024 Change Healthcare cyberattack showed about dependence on a few intermediaries.

The Universal Medical Device Nomenclature System, or UMDNS, is a standard naming system for medical devices that supports identifying, filing, retrieving, and exchanging data about equipment. This post explains how device nomenclatures work, how UMDNS relates to GMDN and the Unique Device Identifier, uses in inventory, recalls, and procurement, and what nurses should know.

System integration is the work of assembling separate hardware, software, and communication elements so they function together for an intended purpose. This post explains integration approaches, the role of interface engines, standards, and APIs, testing and safety risks, the single-vendor versus best-of-breed tradeoff, and what integration means for nurses at the bedside.