Reminder: Do not include any PHI or PII in Confluence. If you require 508 accessibility assistance or any other support for this system, then please send an email to onc-jira-questions@healthit.gov
...
US CoreQA - ONC Assessment of Ballot Design in US Core | C-CDAQA - ONC Assessment of Ballot Design in C-CDA | ||||||
Category | Fields | Profile | USCDI Terminology Present? (Do Terminology bindings agree with what is declared in USCDI) | ASTP agrees Design covers USCDI Definition? (Yes/No and Date) | Template | USCDI Terminology Present? (Do Terminology bindings agree with what is declared in USCDI) | ASTP agees agrees Design covers USCDI Definition? (Yes/No and Date) |
Clinical Notes | |||||||
Emergency Department Note Operative Note | US Core Document Reference Profile | Yes - the 2 LOINC codes added to minumum set servers SHALL support declared on the Clinical Notes Guidance page | 28-Nov-24: Yes | Note Activity | Yes - the LOINC codes are already present in the existing Note Types value set. Template description update to reflect USCDI Narrative Note Types | 19-Nov-24: Yes | |
Immunizations | |||||||
Lot Number | US Core Immunization Profile | NA | 28-Nov-24: Yes | Immunization Medication Information | NA | 19-Nov-24: Yes | |
Observations | |||||||
Advance Directive Observation | NA | 28-Nov-24: Yes | NA | 19-Nov-24: Yes Alex suggested that an Invariant be added, so that if answer is "No" to the Existence of an Advance Directive, that there are no Advance Directive Observations contained in Advance Directive Existence Observation Gay will follow-up with the Dev Team to see if that can been done prior to ballot or via a ballot comment during the ballot process. | |||
Sex Parameter for Clinical Use | Sex Parameter for Clinical Use used in US Core patient | Yes - the team previously agreed that
| 28-Nov-24: Yes | Sex Parameter For Clinical Use Observation | Yes - LOINC: 99501-9 Sex parameter for clinical use And THO set Sex Parameter for Clinical Use | 19-Nov-24: Yes | |
Order | |||||||
Medication Order | US Core MedicationRequest ProfileNA | NA RxNorm - Is used- see Medication Clinical Drug @ MedicationRequest.medication | 28-Nov-24: Yes | NA RxNorm is used - see Medication Order: RxNorm - Yes - see Medication Clinical Drug in Medication Information | 19-Nov-24: Yes | ||
Laboratory Order | US Core ServiceRequest Profile | NA (Note Table of Additional Bindings provided: Common LOINC Lab Codes) | 28-Nov-24: Yes | NA (Note "AdditonalAdditional" binding provided Common LOINC Lab Codes) | 19-Nov-24: Yes | ||
Diagnositic Imaging Order | US Core ServiceRequest Profile | NA (Note Table of Additional Bindings provided: Radiology Procedures | 28-Nov-24: Yes | NA (Note "AdditonalAdditional" binding provided provided Radiology Procedures | 19-Nov-24: Yes | ||
Clinical Test Order | US Core ServiceRequest Profile | NA (Note Table of Additional Bindings provided: Clinical Tests | 28-Nov-24: Yes | NA (Note "AdditonalAdditional" binding provided Clinical Tests | 19-Nov-24: Yes Re: Clinical Tests value set. This value set is Clinical LOINC codes minus radiology codes with multiple classes excluded for codes that do not fit the conceptual idea of clinical test. The binding is an "Additional" binding or "Preferred" type and is intended to provide an idea od what a "clinical test" is as there has been much discussion over the past year about is "fuzziness" as a type of test (or result). Gay noted that Al and Carmela have noted codes that do not seem appropropriate in the set and is hoping that Al and Carmela will provide that feedback and she will adjust the set accordingly. Preferably this will be done before ballot. 11/22/202: Gay and Al Taylor revised set to remove codes not considered clinical tests | ||
Procedure Order | US Core ServiceRequest Profile | NA (Note Procedure.code bound to same set as Procedure: US Core Procedure Codes) | 28-Nov-24: Yes | NA (Note Procedure.code bound to same set as Procedure: US Core Procedure Codes) | 19-Nov-24: Yes | ||
Patient Demographics/Information | |||||||
Interpreter Needed | US Core Interpreter Needed Extension in US Core Encounter Profile and US Core Patient Profile | Yes - LOINC or SNOMED:
| 28-Nov-24: Yes | Interpreter Needed Observation | Yes - LOINC or SNOMED:
| 28-Nov-24: Yes | |
Pronouns | Individual Pronouns in US Core Patient Profile | NA
| 28-Nov-24: Yes | Individual Pronoun Observation | NA
| 28-Nov-24: Yes | |
Name to Use | Guidance in US Core Patient Profile:
| NA | 28-Nov-24: Yes Gay gave the heads up that the name part qualifier concepts/terms are different in CDA vs FHIR and do not quite align. FHIR trackers have been placed (PA WG) to address this in the future. For now (in both standards) "Name to use" is adequately represented. | US Realm Patient Name (PTN.US.FIELDED) | NA
| 28-Nov-24: Yes Gay gave the heads up that the name part qualifier concpets/terms are different in CDA vs FHIR and do not quite align. FHIR trackers have been placed (PA WG) to address this in the future. For now (in both standards) "Name to use" is adequately represented. | |
Provenance | |||||||
Author | See New Provenance Guidance | NA | 28-Nov-24: Yes | Provenance - Author Participation | NA | 28-Nov-24: Yes | |
Author Role | NA Healthcare Provider Taxonomy use to represent Practitioner role | 28-Nov-24: Yes Gay and Brett advised the ASTP team to review the new Provenance approach and guidance (identified by green highlight and let us know about any concerns, | Provenance - Author Participation (author.code) | NA
Additional Bindings:
| 28-Nov-24: Yes |