USCDI Export for the Public

The pregnancy risk data element is represented by the LOINC code: 42838-3 with the variable values of: • Improved • Deteriorated • Stabilized

LOINC codes are available for gestational age

The pregnancy risk data element is represented by the LOINC code: 42838-3 with the variable values of: • Improved • Deteriorated • Stabilized

Encounter type/occurrence: SNOMED CT (example, value set OID: 2.16.840.1.113883.3.666.5.307) HCPCS (example, value set OID: 2.16.840.1.113883.3.464.1003.101.12.1087) CPT (example, value set OID: 2.16.840.1.113883.3.464.1003.101.12.1001) HL7 value set, encounter type: https://www.hl7.org/fhir/us/core/ValueSet-us-core-encounter-type.html Encounter Diagnosis/ Primary Diagnosis/Discharge Diagnosis: SNOMED CT ICD-10-CM Discharge Disposition: DischargeDisposition Code System http://terminology.hl7.org/CodeSystem/discharge-disposition Encounter Location: SNOMED HSLOC

Encounter Status: FHIR Encounter Status: http://hl7.org/fhir/ValueSet/encounter-status Classification of Encounter: V3 Value SetActEncounterCode: http://hl7.org/fhir/ValueSet/v3-ActEncounterCode Encounter Type: FHIR Encounter type: http://www.ama-assn.org/go/cpt Encounter participant type: FHIR Participant type: http://hl7.org/fhir/ValueSet/encounter-participant-type Reason for the encounter: FHIR Encounter Reason Codes: http://hl7.org/fhir/ValueSet/encounter-reason Hospital encounter discharge disposition: FHIR Discharge disposition: http://hl7.org/fhir/ValueSet/encounter-discharge-disposition Expected source(s) of payment for this encounter: FHIR Coverage Type and Self-Pay Codes: http://hl7.org/fhir/R4/valueset-coverage-type.html Encounter chief complaint: FHIR DiagnosisRole: http://hl7.org/fhir/R4/valueset-diagnosis-role.html

LOINC codes for vitals—date and timestamps collected in standard format

NPPES assigns a unique number to each registered provider DEA assigns a number to each requesting and qualified healthcare professional.

NPPES assigns a unique number to each registered provider DEA assigns a number to each requesting and qualified healthcare professional.

Encounter Status: FHIR Encounter Status: http://hl7.org/fhir/ValueSet/encounter-status Classification of Encounter: V3 Value SetActEncounterCode: http://hl7.org/fhir/ValueSet/v3-ActEncounterCode Encounter Type: FHIR Encounter type: http://www.ama-assn.org/go/cpt Encounter participant type: FHIR Participant type: http://hl7.org/fhir/ValueSet/encounter-participant-type Reason for the encounter: FHIR Encounter Reason Codes: http://hl7.org/fhir/ValueSet/encounter-reason Hospital encounter discharge disposition: FHIR Discharge disposition: http://hl7.org/fhir/ValueSet/encounter-discharge-disposition Expected source(s) of payment for this encounter: FHIR Coverage Type and Self-Pay Codes: http://hl7.org/fhir/R4/valueset-coverage-type.html Encounter chief complaint: FHIR DiagnosisRole: http://hl7.org/fhir/R4/valueset-diagnosis-role.html

Encounter Status: FHIR Encounter Status: http://hl7.org/fhir/ValueSet/encounter-status Classification of Encounter: V3 Value SetActEncounterCode: http://hl7.org/fhir/ValueSet/v3-ActEncounterCode Encounter Type: FHIR Encounter type: http://www.ama-assn.org/go/cpt Encounter participant type: FHIR Participant type: http://hl7.org/fhir/ValueSet/encounter-participant-type Reason for the encounter: FHIR Encounter Reason Codes: http://hl7.org/fhir/ValueSet/encounter-reason Hospital encounter discharge disposition: FHIR Discharge disposition: http://hl7.org/fhir/ValueSet/encounter-discharge-disposition Expected source(s) of payment for this encounter: FHIR Coverage Type and Self-Pay Codes: http://hl7.org/fhir/R4/valueset-coverage-type.html Encounter chief complaint: FHIR DiagnosisRole: http://hl7.org/fhir/R4/valueset-diagnosis-role.html

Encounter Status: FHIR Encounter Status: http://hl7.org/fhir/ValueSet/encounter-status Classification of Encounter: V3 Value SetActEncounterCode: http://hl7.org/fhir/ValueSet/v3-ActEncounterCode Encounter Type: FHIR Encounter type: http://www.ama-assn.org/go/cpt Encounter participant type: FHIR Participant type: http://hl7.org/fhir/ValueSet/encounter-participant-type Reason for the encounter: FHIR Encounter Reason Codes: http://hl7.org/fhir/ValueSet/encounter-reason Hospital encounter discharge disposition: FHIR Discharge disposition: http://hl7.org/fhir/ValueSet/encounter-discharge-disposition Expected source(s) of payment for this encounter: FHIR Coverage Type and Self-Pay Codes: http://hl7.org/fhir/R4/valueset-coverage-type.html Encounter chief complaint: FHIR DiagnosisRole: http://hl7.org/fhir/R4/valueset-diagnosis-role.html

The information determined as a result of making the observation. The information carried by Observation.value may take several forms, depending on the nature of the observation. For example, it could be a quantitative result, and ordinal scale value, nominal or categorial value, etc. Data Type: variable. Possible data types include: Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period Terminology Standards: The appropriate terminology depends on the observation. A few examples: • If the observation is quantitative, then Observation.value.units SHALL be drawn from UCUM. • If the observation represents a validated assessment instrument (e.g. survey) item and the value is a CodeableConcept, then Observation.value.code SHALL be drawn from LOINC. • If the observation pertains to clinical genetics, then other terminologies or syntaxes may be used as appropriate, e.g. HGVS, ClinVar, etc. • If the observation represents a human phenotype, then the Observation.value MAY be drawn from the Human Phenotype Ontology • If the observation has a nominal or ordinal scale value and the Observation.value exists in SNOMED CT, then SNOMED CT MAY be used.

Vocabulary Standard: No single vocabulary covers the content necessary for representing all aspects of observation reporting (observation identifiers, coded observation values, computable units of measure, etc). Yet, the collection of core vocabularies needed are sufficiently mature. [Observation: Code] LOINC was specifically designed to fulfill the need for a freely available standard for identifying observations. More than 25 years later, it now contains a rich catalog of variables, answer lists, and the collections that contain them. [Observation: Value.units] UCUM was specifically designed to fulfill the need for a freely available standard of computable units of measure. [Observation: Value.code] • If the observation represents a validated assessment instrument (e.g. survey) item and the value is a CodeableConcept, then Observation.value.code SHALL be drawn from LOINC. • If the observation pertains to clinical genetics, then other terminologies or syntaxes may be used as appropriate, e.g. HGVS, ClinVar, etc. • If the observation represents a human phenotype, then the Observation.value MAY be drawn from the Human Phenotype Ontology • If the observation has a nominal or ordinal scale value and the Observation.value exists in SNOMED CT, then SNOMED CT MAY be used Exchange and Analytic CDM specifications: HL7 Version 2: Chapter 7 C-CDA: Results Section (entries required): 2.16.840.1.113883.10.20.22.2.3.1 FHIR: Observation OMOP: Measurement, Observation PCORnet CDM: LAB_RESULT_CM, PRO_CM, OBS_CLIN, OBS_GEN

The concept identifying what was tested, measured, or observed. Data Type: CodeableConcept Permissible Values: The observation identifier SHALL be from LOINC if the concept is present in LOINC.

Vocabulary Standard: No single vocabulary covers the content necessary for representing all aspects of observation reporting (observation identifiers, coded observation values, computable units of measure, etc). Yet, the collection of core vocabularies needed are sufficiently mature. [Observation: Code] LOINC was specifically designed to fulfill the need for a freely available standard for identifying observations. More than 25 years later, it now contains a rich catalog of variables, answer lists, and the collections that contain them. [Observation: Value.units] UCUM was specifically designed to fulfill the need for a freely available standard of computable units of measure. [Observation: Value.code] • If the observation represents a validated assessment instrument (e.g. survey) item and the value is a CodeableConcept, then Observation.value.code SHALL be drawn from LOINC. • If the observation pertains to clinical genetics, then other terminologies or syntaxes may be used as appropriate, e.g. HGVS, ClinVar, etc. • If the observation represents a human phenotype, then the Observation.value MAY be drawn from the Human Phenotype Ontology • If the observation has a nominal or ordinal scale value and the Observation.value exists in SNOMED CT, then SNOMED CT MAY be used Exchange and Analytic CDM specifications: HL7 Version 2: Chapter 7 C-CDA: Results Section (entries required): 2.16.840.1.113883.10.20.22.2.3.1 FHIR: Observation OMOP: Measurement, Observation PCORnet CDM: LAB_RESULT_CM, PRO_CM, OBS_CLIN, OBS_GEN

The assessment and monitoring of goals and goal progress.

Examples for goal assessments include Goal Attainment Scaling (GAS) and patient-reported outcome measures (PROMs) such as PHQ-9, GAD-7 or PROMIS.

Standardized goal assessment tools exist and have associated LOINC terminology codes.

Examples:
• 107332-9-- Goal attainment scale – Reported
• 107334-5 -- Patient follow-up goal attainment scaling score
• 107333-7-- Practitioner follow-up goal attainment scaling score
• 77854-8 -- PROMIS© Ability to Participate in Social Roles and Activities - Short Form v2.0 - 8a
• 92418-3 -- PROMIS© Self-Efficacy for Managing Medications and Treatments - Short Form v1.0 - 8a
• 70274-6-- General Anxiety Disorder (GAD) - 7
• 44261-6 -- PHQ-9

The time or time-period the observed value is asserted as being true. For biological subjects (e.g. human patients) this is typically called the "physiologically relevant time", which is usually either the time of the procedure or of specimen collection. Very often the source of the date/time information is not known, only the date/time itself. Data Type: variable. Allowable data types include: dateTime, Period, Timing, instant Note: An observation time is essential for understanding the context and clinical meaning of an observation. For nationwide interoperability, systems must support the ability to representing this time, even if it is not present for all observations.

Vocabulary Standard: No single vocabulary covers the content necessary for representing all aspects of observation reporting (observation identifiers, coded observation values, computable units of measure, etc). Yet, the collection of core vocabularies needed are sufficiently mature. [Observation: Code] LOINC was specifically designed to fulfill the need for a freely available standard for identifying observations. More than 25 years later, it now contains a rich catalog of variables, answer lists, and the collections that contain them. [Observation: Value.units] UCUM was specifically designed to fulfill the need for a freely available standard of computable units of measure. [Observation: Value.code] • If the observation represents a validated assessment instrument (e.g. survey) item and the value is a CodeableConcept, then Observation.value.code SHALL be drawn from LOINC. • If the observation pertains to clinical genetics, then other terminologies or syntaxes may be used as appropriate, e.g. HGVS, ClinVar, etc. • If the observation represents a human phenotype, then the Observation.value MAY be drawn from the Human Phenotype Ontology • If the observation has a nominal or ordinal scale value and the Observation.value exists in SNOMED CT, then SNOMED CT MAY be used Exchange and Analytic CDM specifications: HL7 Version 2: Chapter 7 C-CDA: Results Section (entries required): 2.16.840.1.113883.10.20.22.2.3.1 FHIR: Observation OMOP: Measurement, Observation PCORnet CDM: LAB_RESULT_CM, PRO_CM, OBS_CLIN, OBS_GEN

The patient, or group of patients, location, or device this Observation is about and into whose record the observation is placed. Note: Additional structures are needed to handle situations where the actual focus of the Observation is different from the subject (or a sample of, part, or region of the subject). For example, a measurement on a fetus that is placed in the mother's record. Data Type: Reference (Patient, Group, Device, or Location). This data element is typically a pointer into a record in another table/structure that contains more metadata about the subject. Note: This Data Element (Observation.subject) would typically point to a record/instance of the Patient Demographics Data Class, though Observations can be recorded for other “units of analysis” (such as a geographic area, group of subjects, etc). The exact mechanism for specifying this linkage is not prescribed, but the purpose of this Data Element is to establish that the ability to communicate “who the observation is about” must be supported.

Vocabulary Standard: No single vocabulary covers the content necessary for representing all aspects of observation reporting (observation identifiers, coded observation values, computable units of measure, etc). Yet, the collection of core vocabularies needed are sufficiently mature. [Observation: Code] LOINC was specifically designed to fulfill the need for a freely available standard for identifying observations. More than 25 years later, it now contains a rich catalog of variables, answer lists, and the collections that contain them. [Observation: Value.units] UCUM was specifically designed to fulfill the need for a freely available standard of computable units of measure. [Observation: Value.code] • If the observation represents a validated assessment instrument (e.g. survey) item and the value is a CodeableConcept, then Observation.value.code SHALL be drawn from LOINC. • If the observation pertains to clinical genetics, then other terminologies or syntaxes may be used as appropriate, e.g. HGVS, ClinVar, etc. • If the observation represents a human phenotype, then the Observation.value MAY be drawn from the Human Phenotype Ontology • If the observation has a nominal or ordinal scale value and the Observation.value exists in SNOMED CT, then SNOMED CT MAY be used Exchange and Analytic CDM specifications: HL7 Version 2: Chapter 7 C-CDA: Results Section (entries required): 2.16.840.1.113883.10.20.22.2.3.1 FHIR: Observation OMOP: Measurement, Observation PCORnet CDM: LAB_RESULT_CM, PRO_CM, OBS_CLIN, OBS_GEN

This data element carries information on Self-care that is exchanged as observations. (Observations are characteristics that can be tested, measured, or observed and are communicated with a name-value pair structure). Self-care is a broad domain. Using the conceptual framework of the the International Classification of Function (ICF), it includes aspects such as eating, caring for teeth, putting clothes on, etc. Notes: • This data element is constrained to health data represented in data structures for observations. Observations should be represented using terminologies supporting this conceptual model, such as LOINC, which is designed for this purpose. Representing problems, goals, and other types of information related to functioning should use other data class structures as appropriate. • Examples of Self-care concepts can be found in the ICF browser at: https://apps.who.int/classifications/icfbrowser • Examples of demonstrated use of Self-care data can be found in the PACIO FHIR Functional Status Implementation Guide which supports exchange of observation data such as eating, oral hygiene, upper body dressing using assessments coded with LOINC.

LOINC. LOINC is a freely available global standard that contains a well-developed model for representing variables, answer lists, and the collections that contain them.* Many clinical assessments, scales, and other observations related to functioning are present in LOINC, including all of the variables on the PAC assessments for SNFs, IRFs, LTCHs, and HHAs. Regenstrief operates a robust process for adding new content (including functioning assessment instruments) if key gaps are identified. *PMID: 22899966

The date when the prescription was initially written or authored.

Date Medication Prescribed and Date Medication Administered: dateTime Data Type (FHIR): http://hl7.org/fhir/datatypes.html#dateTime Medication Prescribed Code and Medication Administered Code: RxNorm: https://www.nlm.nih.gov/research/umls/rxnorm/index.html Medication Prescribed Dose Units and Medication Administration Dose Units: UCUM: http://unitsofmeasure.org

This data element carries information on Mobility that is exchanged as observations. (Observations are characteristics that can be tested, measured, or observed and are communicated with a name-value pair structure). Mobility is a broad domain. Using the conceptual framework of the International Classification of Function (ICF), it includes aspects such as rolling over, transferring, walking short distances, etc. Notes: • This data element is constrained to health data represented in data structures for observations. Observations should be represented using terminologies supporting this conceptual model, such as LOINC, which is designed for this purpose. Representing problems, goals, and other types of information related to functioning should use other data class structures as appropriate. • Examples of Mobility concepts can be found in the ICF browser at: https://apps.who.int/classifications/icfbrowser • Examples of demonstrated use of Mobility data can be found in the PACIO FHIR Functional Status Implementation Guide which supports exchange of observation data such as roll left and right, car transfer, walk 10 feet using assessments coded with LOINC.

LOINC. LOINC is a freely available global standard that contains a well-developed model for representing variables, answer lists, and the collections that contain them.* Many clinical assessments, scales, and other observations related to functioning are present in LOINC, including all of the variables on the PAC assessments for SNFs, IRFs, LTCHs, and HHAs. Regenstrief operates a robust process for adding new content (including functioning assessment instruments) if key gaps are identified. *PMID: 22899966

A code (or set of codes) that specify this medication, or a textual description if no code is available.

Date Medication Prescribed and Date Medication Administered: dateTime Data Type (FHIR): http://hl7.org/fhir/datatypes.html#dateTime Medication Prescribed Code and Medication Administered Code: RxNorm: https://www.nlm.nih.gov/research/umls/rxnorm/index.html Medication Prescribed Dose Units and Medication Administration Dose Units: UCUM: http://unitsofmeasure.org