USCDI Export for the Public

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

Who recorded the adverse event

HL7.org FHIR R4 v4.0

Location where adverse event occurred

HL7.org FHIR R4 v4.0

Effect on the subject due to the event

HL7.org FHIR R4 v4.0

When the event was recorded

HL7.org FHIR R4 v4.0

Date/Time the event was detected

HL7.org FHIR R4 v4.0

Time period of event – date/time, period, timing when the event occurred

HL7.org FHIR R4 v4.0

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

Clinical notes information for a newborn may include the Labor and delivery summary record under–Infant data, and maternal progress note. Example information will include breastfeeding information at time of discharge.

LOINC codes exist for each of the proposed data elements The clinical notes of an new born should capture information such as: 73756-9 | Infant is being breastfed at discharge

Audiometry/Audiology Audiograms: (68635-2 Audiology Diagnostic study note) Psychology Reports Mental Status Evaluation: (94798-6 Psychology Diagnostic study note) Neuropsychological Testing: (94798-6 Psychology Diagnostic study note) Psychological Testing: (94798-6 Psychology Diagnostic study note) Cardiac Reports Angiogram: (75425-9 Cardiology Diagnostic study note) Cardiac Catheterization: (75425-9 Cardiology Diagnostic study note) Doppler Test (75425-9 Cardiology Diagnostic study note) Electrocardiograph, electrocardiogram (EKG/ECG) result/interpretation: (75425-9 Cardiology Diagnostic study note) EKG/ECG Tracing Image: (75425-9 Cardiology Diagnostic study note) Echocardiogram result/interpretation: (75425-9 Cardiology Diagnostic study note) Stress Testing (exercise, pharma): (83539-7 Cardiology Risk assessment & screening note) Holter monitor: (83539-7 Cardiology Risk assessment & screening note) Neurology Electroencephalogram (EEG): (68556-0 Neurology Diagnostic study note) Electromyogram/nerve conduction (EMG): (68556-0 Neurology Diagnostic study note) Myelogram: (68556-0 Neurology Diagnostic study note) Ophthalmology/Optometry Visual Acuity: (78573-3 Ophthalmology Diagnostic study note) Visual Fields: (78573-3 Ophthalmology Diagnostic study note) Radiology (Interpretations Only; No Images) CT: (68604-8 Ophthalmology Diagnostic study note) MRI: (68604-8 Ophthalmology Diagnostic study note) PET: (68604-8 Ophthalmology Diagnostic study note) X-Ray: (68604-8 Ophthalmology Diagnostic study note) Respiratory DLCO Study: (80792-5 Pulmonary Diagnostic study note) Pulmonary Function Study: (80792-5 Pulmonary Diagnostic study note) Spirometry Test result/interpretation: (80792-5 Pulmonary Diagnostic study note) Spirometry Tracing Image: (80792-5 Pulmonary Diagnostic study note) Surgical Diagnostics Bone Marrow (Biopsy/Aspiration): (48807-2 Bone marrow aspiration report) Colonoscopy: (18746-8 Colonoscopy study report) Endoscopy: (18751-8 Endoscopy study report) Additional Procedures Ultrasound (exclude Doppler): (59282-4 Stress cardiac echo study report) Genetic Testing: (51969-4 Genetics analysis report) Physical Exam: (29545-1 Physical findings narrative)

LOINC—although we would like to see the set of codes constrained as suggested above. In Data Element Description above, we have the suggested LOINC code (showing also the Long Common Name) for each Note in our list. Such constraints are needed in order to allow for semantic interoperability.

Documentation sent to a consultant, for example, by a primary care provider, summarizing the patient’s clinical history and reason for consult.

LOINC. We recommend adding the new data elements with a LOINC term representing the most generic term for that particular data element, along with information about how to access the value set of more specific LOINC terms available for each note type. The Regenstrief LOINC team can provide FHIR ValueSets with associated OIDs and/or webpages with downloadable content for each note type. Both of these resources would include the same set of LOINC terms. These resources do not exist yet but can easily be created if approved as additions to the USCDI. The benefit of hosting these resources on the LOINC website or providing them via LOINC FHIR terminology services compared to VSAC or other value set repositories is that the resources will be updated automatically with every LOINC release and would not require a separate process.

Cause of death information includes the sequence of events leading to death as well as other conditions significantly contributing to death. The underlying cause of death may be different than the terminal condition. This may include summary of death note, and/or death information that may be captured within the discharge summary note or other cause of death documentation within the clinical notes section.

LOINC: Summary of death note: 47046-8: https://loinc.org/47046-8/ Physician Summary of death note: 83796-3: https://loinc.org/83796-3/ Nurse Summary of death note: 84273-2: https://loinc.org/84273-2/ US Standard Certificate of Death: https://www.cdc.gov/nchs/data/dvs/DEATH11-03final-ACC.pdf Hepatitis C Case Report Form: https://www.cdc.gov/hepatitis/pdfs/HepatitisCaseRprtForm.pdf Supporting Links: PHINVADS Value Set: https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.3593

The custodian is the organization that is in charge of maintaining and is entrusted with the care of the document.

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

A clinical note which narratively summarizes the patient encounter. LOINC code = 67781-5.

LOINC https://loinc.org/67781-5/ https://loinc.org/28636-9/ https;//loinc.org/34108-1/

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

Date and timestamps associated with the completion of laboratory results, that are meta data associated with laboratory results

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