HIMSS CPHIMS, AHIMA RHIA & HL7/FHIR Health IT practice drill
10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.
Sample questions
An interface analyst is configuring HL7 v2.x pipe-delimited feeds between an acute care hospital's EHR and its laboratory information system (LIS). Which pairing accurately distinguishes the message event type used when a patient is admitted from the message event type used to transmit completed lab values back to the EHR?
ORU^R01 transmits inpatient admission demographics in PV1 segments, while ADT^A01 returns structured lab results in OBX segments.
ADT^A04 transmits inpatient admission events using FHIR JSON payloads, while ORM^O01 returns finalized chemistry observations.
SIU^S12 transmits inpatient admission demographics across pipe-delimited segments, while DFT^P03 returns automated laboratory results.
Show the answer
C. ADT^A01 conveys inpatient admission demographics (MSH, PID, PV1), while ORU^R01 returns lab results (OBR, OBX).
In HL7 v2.x pipe-delimited messaging, ADT^A01 (Admit/Visit Notification) conveys inpatient admission and demographic data via MSH, PID, and PV1 segments, whereas ORU^R01 (Unsolicited Observation Result) delivers completed diagnostic and laboratory results using OBR (Observation Request) and OBX (Observation/Result) segments. ORM^O01 is used for orders, SIU^S12 for scheduling, and DFT^P03 for financial charges.
A health system integrates a third-party hypertension management application that launches directly from a clinician's EHR chart to retrieve the active patient's demographics and recent blood pressure readings. Which architecture and authorization mechanism complies with SMART on FHIR standards?
RESTful HTTP GET requests to FHIR Patient and Observation resources authorized via OAuth 2.0 EHR launch context and scoped access tokens.
Pipe-delimited HL7 v2 query messages transmitted over SFTP using shared clinician directory passwords stored inside the external application.
SOAP XML envelope calls to monolithic CDA document repositories authenticated through static vendor API keys with unrestricted read-write access.
Direct SQL read queries against the EHR relational production database authenticated with an enterprise service account covering all patients.
Show the answer
A. RESTful HTTP GET requests to FHIR Patient and Observation resources authorized via OAuth 2.0 EHR launch context and scoped access tokens.
HL7 FHIR exposes modular clinical data—such as Patient and Observation resources—over RESTful HTTP APIs in JSON or XML format. SMART on FHIR layers OAuth 2.0 (and OpenID Connect for user identity) over FHIR so EHR-launched apps receive a launch context and tightly scoped bearer tokens (e.g., patient/Observation.read) rather than sharing passwords or granting broad database access.
A clinical informatics architect is mapping structured EHR data elements to USCDI-required national reference terminologies for interoperability across FHIR and C-CDA interfaces. Which mapping correctly pairs problem list clinical concepts, laboratory test names, and active medication orders?
SNOMED CT for clinical problem concepts, LOINC for laboratory observations, and RxNorm for normalized medications.
LOINC for clinical problem concepts, SNOMED CT for laboratory test codes, and ICD-10-PCS for outpatient medication orders.
RxNorm for clinical problem concepts, CPT for laboratory observation names, and SNOMED CT for normalized drug ingredients.
SNOMED CT for laboratory observation names, RxNorm for inpatient clinical findings, and LOINC for active medication strengths.
Show the answer
A. SNOMED CT for clinical problem concepts, LOINC for laboratory observations, and RxNorm for normalized medications.
Under ONC USCDI and HL7 interoperability standards, SNOMED CT encodes granular clinical concepts such as diagnoses, findings, and problem list entries; LOINC (Logical Observation Identifiers Names and Codes) identifies laboratory tests, vital signs, and clinical measurements; and RxNorm provides normalized identifiers for clinical drugs linking active ingredients, strengths, and dose forms.