Date

28 Nov 2023

Attendees

Attendee	Name	Affiliation
	Alex Kontur	ONC Public Health Analyst (COR)
	Brett Marquard	HL7 US Realm Senior Advisor
	Matthew Rahn	Director, Standards Division
	Gay Dolin	HL7 US Realm PM
	Carmela Minicucci Couderc	ONC - Branch Chief, Terminology and Content Delivery
	Albert W. Taylor	ONC - Medical Informatics Officer

Goals

Confirmation of ONC understanding of USCDI Design in US Core and C-CDA that is going to ballot
Link to public HL7 Core Tracker (USCDI v4 only)
- US Core Build Site
Link to public HL7 C-CDA Tracker (USCDI v1-V4)
- C-CDA Build Site

USCDI v4 QA Table

		QA - ONC Assessment of Ballot Design in US Core		QA - ONC Assessment of Ballot Design in C-CDA
Category	Fields	USCDI Terminology Present? (Do Terminology bindings agree with what is declared in USCDI)	Design covers USCDI Definition?	USCDI Terminology Present? (Do Terminology bindings agree with what is declared in USCDI)	Design covers USCDI Definition?
Allergies and Intolerances
	Substance (Non-Medication)	Yes	Yes	Yes	Yes
Encounter Information
	Encounter Identifier	yes	yes	No terminology required in USCDI	Yes
Facility Information
	Facility Identifier	yes	yes	No terminology required in USCDI	Yes
	Facility Type	yes	yes	No terminology required in USCDI	Yes
	Facility Name	yes	yes	No terminology required in USCDI	Yes
Goals and Preferences
	Treatment Intervention Preference	IG notes that the 'treatment-intervention-preference' will be added to LOINC. I assume this means the 'system' value under .code is a placeholder and will be fixed to LOINC when the code is available? The IG also notes that implementers can include additional codes where appropriate (in .code or .category), however it is unclear where these codes would go. The system and code elements of the coding are fixed, is the intent that any additional codes would go in the text element of the codeableConcept?		Goal obs SHOULD use LOINC	unclear
	Care Experience Preference	Similar issue as above: The IG notes that implementers can include additional codes where appropriate (in .code or .category), however it is unclear where these codes would go. The system and code elements of the coding are fixed, is the intent that any additional codes would go in the text element of the codeableConcept?		Goal obs SHOULD use LOINC	unclear
Health Status Assessments
	Alcohol Use			yes	yes
	Substance Use			yes	yes
	Physical Activity			yes	yes
Laboratory
	Result Unit of Measure	The IG provides guidance about "Using UCUM codes in the Quantity datatype". The guidance begins by saying some quantity types are bound to UCUM, however the quantity type in this profile is not bound to UCUM. Should it be bound to UCUM? Does the guidance still apply in cases where a quantity type is not bound to UCUM?		yes	yes
	Result Reference Range	Profile doesn't appear to have any guidance indicating that implementers should use UCUM for this element.		Template doesn't appear to have any guidance indicating that implementers should use UCUM for this element.	yes
	Result Interpretation	yes	yes	yes	yes
	Specimen Source Site	yes	yes	yes	Members of Specimen type 2.16.840.1.113762.1.4.1099.54 concatenate Specimen Type and Specimen Source Site
	Specimen Identifier	yes	yes	No terminology required in USCDI
	Specimen Condition Acceptability	yes	yes	yes	yes
Medications
	Medication Instructions	yes	yes	No terminology required in USCDI	yes
	Medication Adherence			no?	no?
Procedures
	Performance Time	yes	USCDI definition references medication administration...should the USCDI table point to an appropriate profile?	No terminology required in USCDI	yes
Vital Signs				yes	yes
	Average Blood Pressure

Space shortcuts

Page tree

Date

Attendees

Goals

USCDI v4 QA Table

Action items

Space shortcuts

Page tree

2023-12: Review of Profile and Template designs going to January 2024 ballot

Date

Attendees

Goals

USCDI v4 QA Table

Action items