Patient Intake (Medical Intake): Clinical Onboarding Workflows, USCDI Data Classes, and HL7 FHIR Questionnaires

Patient intake—also known as medical intake or a clinical intake assessment—is the structured pre-encounter and point-of-care onboarding workflow through which a healthcare organization collects a patient’s identity, insurance coverage, statutory consents, chief complaint, medical and surgical history, active medications, allergies, and standardized clinical screening questionnaires prior to clinician evaluation. In modern ambulatory clinics, hospitals, and clinical trial sites, digital patient intake replaces paper clipboards with mobile-responsive questionnaires that map directly into discrete Electronic Health Record (EHR) fields via HL7 FHIR APIs.

What Is Patient Intake vs. Administrative Patient Registration?

While the terms are sometimes used interchangeably at the front desk, health informatics architects distinguish between administrative patient registration and comprehensive patient intake (medical intake):

• Administrative Patient Registration: Focuses on Enterprise Master Patient Index (EMPI) identity resolution, demographic capture, real-time ANSI ASC X12N 270/271 insurance eligibility verification, copay collection, and triggering an HL7 v2 ADT^A04 (Register a Patient) or ADT^A01 (Admit/Visit Notification) message.
• Medical Intake (Clinical Intake Assessment): Encompasses both the administrative check-in packet AND the structured clinical history inventory—including chief complaint, History of Present Illness (HPI) prompts, Review of Systems (ROS) checklists, past medical/family/social history (PFSH), medication and allergy reconciliation, Social Determinants of Health (SDOH) screening, and specialty-specific functional or behavioral instruments (such as a Physical Therapy [PT] intake form or PHQ-9/GAD-7 depression and anxiety screens).

Core Domains of a New Patient Medical Intake Workflow

To comply with Office of the National Coordinator for Health Information Technology (ONC) United States Core Data for Interoperability (USCDI) standards and HL7 FHIR US Core Implementation Guide profiles, an end-to-end new patient intake workflow is structured across five data layers:

Intake Workflow Stage	Captured Clinical & Administrative Elements	Target HL7 FHIR R4 Resource & Terminology Standard
1. Demographics & Identity	Legal/preferred name, DOB, address, biological sex, SOGI (sexual orientation & gender identity), OMB race/ethnicity, preferred language	Patient (US Core Patient Profile; LOINC & CDC Race/Ethnicity codes)
2. Coverage & Financial Intake	Front/back insurance card OCR scan, subscriber ID, group number, primary/secondary payer coordination, X12 270/271 eligibility check	Coverage, RelatedPerson, and X12 270/271 transaction sets
3. Statutory & Clinical Consents	HIPAA Notice of Privacy Practices (45 CFR § 164.520) acknowledgment, Consent to Treat, Assignment of Benefits, Telehealth Consent, Research eConsent	Consent and signed PDF DocumentReference with audit timestamp
4. Medical History, Meds & Allergies	Active and resolved problems, surgical history, current prescriptions and OTC supplements, drug/food/latex allergies and reaction severity	Condition (SNOMED CT / ICD-10-CM), MedicationStatement (RxNorm), AllergyIntolerance
5. SDOH & Clinical Screeners	PRAPARE / AHC HRSN social risk screening (food, housing, transportation), tobacco/alcohol use, PHQ-2/PHQ-9, fall-risk, and specialty PROMs	Questionnaire, QuestionnaireResponse, and Observation (LOINC panels)

How HL7 FHIR Structured Data Capture (SDC) Powers Digital Patient Intake

Historically, third-party patient intake portals saved completed patient questionnaires as flat, non-searchable PDF documents uploaded into the EHR’s media tab—forcing medical assistants or nurses to manually re-type problems, allergies, and PHQ-9 scores into discrete EHR flowsheet rows. Modern clinical informatics architectures eliminate manual transcription by implementing the HL7 FHIR Structured Data Capture (SDC) Implementation Guide:

1. Pre-Populating Known Chart Context ($populate): When a returning patient opens a pre-visit SMS or patient portal intake link 24–72 hours before their appointment, the intake engine executes the FHIR SDC $populate operation against the EHR’s FHIR API. Instead of confronting a blank 10-page form, the patient sees their existing problem list, active RxNorm medications, and known allergies and simply confirms or flags changes.
2. Dynamic Branching and LOINC Binding (Questionnaire): The intake form is authored as a FHIR Questionnaire resource using enableWhen branching rules and LOINC question codes (such as LOINC 44249-1 for the PHQ-9 panel or LOINC 93025-5 for the PRAPARE SDOH protocol).
3. Automated Resource Extraction ($extract) with Clinician Reconciliation: Upon submission, the FHIR SDC $extract operation transforms the patient’s QuestionnaireResponse into discrete candidate Condition, AllergyIntolerance, MedicationStatement, and Observation resources staged in the EHR’s intake reconciliation tray for medical assistant and clinician sign-off.

Patient Intake in Clinical Research and Decentralized Trials

In interventional clinical trials and patient registries, the clinical intake workflow serves as the primary gatekeeper for protocol eligibility and regulatory compliance:

• Automated Inclusion / Exclusion Pre-Screening: Digital trial intake questionnaires evaluate study inclusion/exclusion criteria against patient-reported medical history and consumer-authorized FHIR EHR data prior to scheduling an in-person Screening visit.
• 21 CFR Part 50 and Revised Common Rule (45 CFR § 46.116) eConsent: Before any study-specific intake procedures or biospecimen collections occur, the digital intake pipeline presents the IRB-approved Key Information summary, multimedia informed consent document, and HIPAA Authorization (45 CFR § 164.508) for identity-verified electronic signature.

Frequently Asked Questions

What is patient intake?

Patient intake is the pre-visit and point-of-care clinical and administrative onboarding process used to gather a patient’s demographics, insurance eligibility, legal and HIPAA consents, chief complaint, medical and surgical history, active medications, allergies, and standardized screening questionnaires before a healthcare encounter.

What is a medical intake and how does it differ from patient registration?

While patient registration focuses on administrative identity matching (EMPI), scheduling, and insurance billing verification (X12 270/271 and HL7 v2 ADT messaging), a medical intake (clinical intake assessment) captures structured clinical baseline data—such as SNOMED CT conditions, RxNorm medications, allergies, Review of Systems, and LOINC-coded symptom/SDOH questionnaires—mapped into the EHR chart via HL7 FHIR Questionnaire and US Core resources.