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
...
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? GD Comments:
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 GD Comments:
| 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 |
...