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
We will be performing scheduled maintenance on Saturday July 6th, from 8am to 1pm. During this time, users can expect interruptions in services. We thank you for your patience.
Implementation of 90-Day Deactivation Policy
The ONC Jira Core and Confluence support team will soon implement an account deactivation policy for all users who have not logged into the systems within the previous 90-days or more. To avoid the risk of having your account being deactivated, please immediately log into ONC Jira Core and Confluence as soon as possible. Deactivated accounts will be retained, including historic activity. Users are able to reactivate their accounts using the correct credentials used prior to deactivation.Login Support
If you encounter a captcha prompt, login issues, or believe your account may be deactivated and require assistance, please send an email to onc-jira-questions@healthit.govHHS System Login
This warning banner provides privacy and security notices consistent
with applicable federal laws, directives, and other federal guidance
for accessing this Government system, which includes all devices/storage
media attached to this system. This system is provided for
Government-authorized use only. Unauthorized or improper use of this
system is prohibited and may result in disciplinary action and/or civil
and criminal penalties. At any time, and for any lawful Government
purpose, the government may monitor, record, and audit your system usage
and/or intercept, search and seize any communication or data transiting
or stored on this system. Therefore, you have no reasonable expectation
of privacy. Any communication or data transiting or stored on this
system may be disclosed or used for any lawful Government purpose.
Acknowledgements of understanding ofcurrent design approach or public design approachdiscussion plans (attendee names)
Treatment Intervention Preference
LOINC is the USCDI recommended vocabulary. We discussed that pre-existing work also leverages SNOMED finding and procedure codes and even CPT.
The group confirmed that other code systems are allowed to communicate the complete meaning within the profile and that LOINC is intended to be the vocabulary/tool the supports queries to see if such preferences were assessed within an EHR
Other codes systems are allowed (for example) SNOMED as the answers
Care Experience Preference
LOINC is the USCDI recommended vocabulary. We discussed that pre-existing work also leverages SNOMED finding and procedure codes and even CPT.
The group confirmed that other code systems are allowed to communicate the complete meaning within the profile and that LOINC is intended to be the vocabulary/tool the supports queries to see if such preferences were assessed within an EHR
Other codes systems are allowed (for example) SNOMED as the answers
Alcohol Use
(evaluation/questions)
LOINC is the USCDI recommended vocabulary. We discussed that pre-existing work also leverages SNOMED finding and procedure codes and even CPT.
The group confirmed that other code systems are allowed to communicate the complete meaning within the profile and that LOINC is intended to be the vocabulary/tool the supports queries to see if alcohol use was assessed within an EHR
We discussed whether or not specific value sets should be developed or just profiles to be used be identified - options:
Guidance ONLY as to what profile/templates should be used
Develop value sets - but keep bindings loose so that if implementations use questionnaires/forms that aign with concepts not in the value sets, they would be free to use other codes
Carmela is going to check to see if "preferential bindings" are available in R4 (If code A out of value set A is used at observation.code, then answer list C value set is used at observation.value, if If code B out of value set A is used at observation.code, then answer list D value set is used at observation.value
Al mentioned the valuets stewarded by Patient Care might be considered (which are the MCC sets mentioned in the Vocabulary Discrepancies table)
Other codes systems are allowed (for example) SNOMED as the answers
Substance Use
(evaluation/questions)
LOINC is the USCDI recommended vocabulary. We discussed that pre-existing work also leverages SNOMED finding and procedure codes and even CPT.
The group confirmed that other code systems are allowed to communicate the complete meaning within the profile and that LOINC is intended to be the vocabulary/tool the supports queries to see if substance use was assessed within an EHR
We discussed whether or not specific value sets should be developed or just profiles to be used be identified - options:
Guidance ONLY as to what profile/templates should be used
Develop value sets - but keep bindings loose so that if implementations use questionnaires/forms that aign with concepts not in the value sets, they would be free to use other codes
Carmela is going to check to see if "preferential bindings" are available in R4 (If code A out of value set A is used at observation.code, then answer list C value set is used at observation.value, if If code B out of value set A is used at observation.code, then answer list D value set is used at observation.value
Al mentioned the valuets stewarded by Patient Care might be considered (which are the MCC sets mentioned in the Vocabulary Discrepancies table)
Other codes systems are allowed (for example) SNOMED as the answers
Physical Activity
(evaluation/questions)
LOINC is the USCDI recommended vocabulary.
The group confirmed that other code systems are allowed to communicate the complete meaning within the profile and that LOINC is intended to be the vocabulary/tool the supports queries to see if physical activity assessed within an EHR
We discussed whether or not specific value sets should be developed or just profiles to be used be identified - options:
Guidance ONLY as to what profile/templates should be used
Develop value sets - but keep bindings loose so that if implementations use questionnaires/forms that aign with concepts not in the value sets, they would be free to use other codes
Carmela is going to check to see if "preferential bindings" are available in R4 (If code A out of value set A is used at observation.code, then answer list C value set is used at observation.value, if If code B out of value set A is used at observation.code, then answer list D value set is used at observation.value
Other codes systems are allowed (for example) SNOMED as the answers
Lab values/results
SNOMED the USCDI recommended vocabulary. Confirmed that "If encoded" SNOMED is the USCDI recommended vocabulary. (Result may be a Physical Quantity which would be a number plus UCUM to identify the unit)
Vocabulary design is still open and use of SNOMED is likely not a problem to design in, but Gay mentioned that for the "high-level" adherance type of codes, SNOMED uses "compliance" concept names which may be considered offensive to some groups. Carmela mentioned that other words could be used in EHR UIs.
They recognized that the high level SNOMED codes concept names may present challenges during ballot and reconciliation.
TEAM: PLEASE CONFIRM THAT IT IS UNDERSTOOD THAT IN C-CDA THE DESIGN WILL PROBABLY BE A LOINC CODE AT OBSERVATION.VALUE, WITH SNOMED AT OBSERVATION.VALUE
POINT NOT DISCUSSED: CONSIDER ONC REACHING OUT TO SNOMED TO REQUEST CONCEPT NAME CHANGES FROM USING THE WORK "COMPLIANCE" TO "ADHERANCE"
See children of 414059009 | Drug therapy compliance observations (finding) |
Note that some of the terms have "Adherence" as acceptable synonyms
Lab Result Specimen Condition Acceptability Lab Result Interpretation
ONC is not finished discussing these two items. internally. We will resume discussion at the next meeting.
Questions was asked as to why the observation.interpretation discrepancy was more severe than specifmen condition given both HL7 Vocabs have been used in V2 for a very long time.
GD reviewed after and it appeasr both are equally problematic
v2 Specimen Condition is used in the FHIR Core SpecimenResource and is an extensible binding (which means a term from the value set is required to be used unless the terms do not cover the concept)
ObservationInterpretation is used on 2 FHIR Core Resources and +/- 30 Profiles. And is an extensible binding (which means a term from the value set is required to be used unless the terms do not cover the concept)