2015 Edition Certification NPRM Prioritization Recommendations/Standards Readiness Assessment June 8, 2015 Semantic Standards Workgroup Becky Kush, co-chair Jamie Ferguson, co-chair

Membership 1 MembersOrganization Co-Chairs Jamie FergusonKaiser Permanente Rebecca KushClinical Data Interchange Standards Consortium (CDISC) Members John CarterApelon, Inc. Todd CooperBreakthrough Solutions Foundry, Inc., Center for Medical Interoperability Stan Huff Intermountain Healthcare Rosemary KennedyeCare Informatics, LLC, Thomas Jefferson University Harry RhodesAHIMA Eric RoseIntelligent Medical Optics (IMO) John Speakman New York University Langone Medical Center Asif SyedAmerican Medical Association (AMA) Andy Wiesenthal - liaison memberDeloitte Consulting, LLP Ex Officio Members Steve BrownVeterans Administration (VA) Margaret HaberEnterprise Vocabulary Services, National Cancer Institute (NCI) Betsy HumphreysNational Library of Medicine (NLM) Mitra RoccaFood and Drug Administration (FDA) ONC Staff Lead Patricia GreimOffice of the National Coordinator for Health IT

Semantic Standards – Certification Rule Workplan MeetingsTask March 27, :30pm-3:30pm ET HITSC Administrative Meeting Charged by HITSC with commenting on the Certification NPRM April 1, 2015, 12:00pm-1:30pm Certification NPRM Introduction and process for commenting on NPRM April 22, 2015 – HITSC meeting Interoperability Roadmap V.1 comments to the HITSC April 24, :00pm ET Group 2 - Small Group Discussion #1 April 30, :00pm ET Group 2 - Small Group Discussion #2 May 4, 2015, 11:30 -1:00pm Group 2 to report out to full workgroup May 15, 2015, 10:30 -11:30am Group 1 to report out to full workgroup May 18, 2015, 10:00am-11:30am Finalize Comments for both groups 1 & 2 May 20, 2015 – HITSC Meeting Present Certification NPRM Comments to the HITSC  June 8, 2015 – 11:30am-1:00pm Prioritization recommendations for NPRM Standards June 24, 2015 – HITSC Meeting Present prioritization recommendations 2

HITSC Readiness Evaluation and Classification Criteria for Technical Specifications Emerging Standards Pilots National Standards Adoptability Maturity Low Moderate High Maturity Criteria: Maturity of Specification Maturity of Underlying Technology Components Market Adoption Adoptability Criteria: Ease of Implementation and Deployment Ease of Operations Intellectual Property The Metrics the HITSC has adopted for helping to determine when a technology specification is ready to become a national standard full.pdf?%2520ijkey=8oAq1ZTZyQ6edqC&keytype=ref\

Standards Readiness for Inclusion in Certification 4 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H CDT CDT: Code on Dental Procedures and Nomenclature  § (b)(1) – Transitions of care  § (b)(6) – Data portability  § (e)(1) – View, download, and transmit to 3 rd party  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 5 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H CPT-4 CPT - Current Procedural Terminology  § (b)(1) – Transitions of care  § (b)(6) – Data portability  § (e)(1) – View, download, and transmit to 3 rd party  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 6 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H ICD-10-PCS the 10th revision of the International Statistical Classification of Diseases and Related Health Problems (ICD), § (b)(1) – Transitions of care  § (b)(6) –Data portability  § (e)(1) – View, download, and transmit to 3 rd party  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H Logical Observation Identifiers Names and Codes (LOINC ® ) Database version 2.50 Logical Observation Identifiers Names and Codes (LOINC®) Database version 2.50  § (a)(2) - Computerized provider order entry – laboratory  § (a)(6) – Vital signs, body mass index, and growth charts  § (a)(21) – Social, psychological, and behavioral data  § (b)(1) – Transitions of care  § (b)(4) – Incorporate laboratory tests and values/results  § (b)(5) – Transmission of laboratory test reports

Standards Readiness for Inclusion in Certification 8 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H Logical Observation Identifiers Names and Codes (LOINC ® ) Database version 2.50 Logical Observation Identifiers Names and Codes (LOINC®) Database version 2.50 CONTINUED  § (b)(6) – Data portability  § (e)(1) – View, download, and transmit to 3 rd party  § (f)(3) – Transmission to public health agencies – reportable laboratory tests and values/results  § (f)(4) – Transmission to cancer registries  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H “Race & Ethnicity – CDC” code system in the PHIN Vocabulary Access and Distribution System (VADS), Release CDC Race & Ethnicity  § (a)(5) – Demographics  § (b)(1) – Transitions of care  § (b)(6) – Data portability  § (c)(4) – Clinical quality measures – filter  § (e)(1) – View, download, and transmit to 3 rd party  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 10 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H The Office of Management and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 OMB Race and Ethnicity  § (a)(5) – Demographics  § (b)(1) – Transitions of care  § (b)(6) – Data portability  § (e)(1) – View, download, and transmit to 3 rd party  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 11 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H Birth sex must be coded in accordance with HL7 Version 3 attributed as follows: (i) Male. M (ii) Female. F (iii) Unknown. UNK § (a)(5) – Demographics § (a)(6) – Vital signs, body mass index, and growth charts § (a)(21) – Social, psychological, and behavioral data § (b)(1) – Transitions of care § (b)(6) – Data portability § (c)(4) – Clinical quality measures – filter § (e)(1) – View, download, and transmit to 3 rd party § (g)(6) – Consolidated CDA creation performance § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 12 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H HL7 Version 3 attributed as follows:  Other. nullFlavor OTH  Asked but unknown. nullFlavor ASKU  § (a)(21) – Social, psychological, and behavioral data

Standards Readiness for Inclusion in Certification 13 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H The Unified Code of Units of Measure, Revision 1.9 UCUM Unified Codes for Measure  § (a)(6) – Vital signs, body mass index, and growth charts  § (a)(21) – Social, psychological, and behavioral data  § (b)(1) – Transitions of care  § (b)(6) – Data portability  § (e)(1) – View, download, and transmit to 3 rd party  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H HL7 Version 3 Implementa tion Guide: Family History/Pedi gree Interoperab ility HL7 V3  § (a)(15) – Family health history - pedigree

Standards Readiness for Inclusion in Certification 15 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H International Health Terminology Standards Development Organisation (IHTSDO) Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT®), U.S. Edition, September 2014 Release International Health Terminology Standards Development Organization  § (a)(7) – Problem List  § (a)(12) – Smoking Status  § (a)(14) – Family Health History  § (a)(21) – Social, psychological, and behavioral data  § (b)(1) – Transitions of care  § (b)(2) – Clinical information reconciliation and incorporation  § (b)(6) – Data portability

Standards Readiness for Inclusion in Certification 16 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H International Health Terminology Standards Development Organisation (IHTSDO) Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT®), U.S. Edition, September 2014 Release International Health Terminology Standards Development Organization CONTINUED  § (c)(4) – Clinical quality measures – filter  § (e)(1) – View, download, and transmit to 3 rd party  § (f)(3) –Transmission to public health agencies – reportable laboratory tests and values/results  § (f)(4) – Transmission to cancer registries  § (g)(6) – Consolidated CDA creation performance  § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 17 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H The National Council for Prescription Drug Programs Formulary and Benefits Standard, Implementation Guide, Version 3, Release 0 (Version 3.0), April 2012 NCPDP § (a)(11) – Drug formulary and preferred drug list checks

Standards Readiness for Inclusion in Certification Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H HL7 Implementation Guide for CDA ® Release 2: Consolidated CDA Templates for Clinical Notes, Draft Standard for Trial Use, Release 2.0 Consolidated CDA § (b)(1) – Transitions of care § (b)(2) – Clinical information reconciliation and incorporation § (b)(6) – Data portability § (b)(7) – Data segmentation for privacy – send § (b)(9) – Care plan § (e)(1) – View, download, and transmit to 3 rd party § (g)(6) – Consolidated CDA creation performance § (g)(7) – Application access to Common Clinical Data Set § (i)(1) – Electronic submission of medical documentation

Standards Readiness for Inclusion in Certification 19 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H ICD-10-CM § (b)(1) – Transitions of care § (b)(6) – Data portability SCRIPT Standard, Implementatio n Guide, Version 10.6, October, 2008 § (b)(3) – Electronic prescribing

Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H RxNorm, a standardized nomenclature for clinical drugs produced by the United States National Library of Medicine, February 2, 2015 Release RxNorm § (b)(1) – Transitions of care § (b)(2) – Clinical information reconciliation and incorporation § (b)(3) – Electronic prescribing § (b)(6) – Data portability § (e)(1) – View, download, and transmit to 3 rd party § (g)(6) – Consolidated CDA creation performance § (g)(7) – Application access to common clinical data set Standards Readiness for Inclusion in Certification

21 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H HL7 Standard Code Set CVX—Vaccines Administered, updates through February 2, 2015 § (b)(1) – Transitions of care § (b)(6) – Data portability § (e)(1) – View, download, and transmit to 3 rd party § (f)(1) – Transmission to immunization registries § (g)(6) – Consolidated CDA creation performance § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 22 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H National Drug Code Directory– Vaccine Codes, updates through January 15, 2015 § (b)(1) – Transitions of care § (b)(6) – Data portability § (e)(1) –View, download, and transmit to 3 rd party § (f)(1) – Transmission to immunization registries § (g)(6) – Consolidated CDA creation performance § (g)(7) – Application access to common clinical data set

Standards Readiness for Inclusion in Certification 23 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H PHIN Messaging Guide for Syndromic Surveillance: Emergency Department, Urgent, Ambulatory Care, and Inpatient Settings, Release 2.0 § (f)(2) – Transmission to public health agencies – syndromic surveillance HL7 Version Implementation Guide: Electronic Laboratory Reporting to Public Health, Release 2 (US Realm), Draft Standard for Trial Use, Release 1.1 § (f)(3) – Transmission to public health agencies – reportable laboratory tests and values/results

Standards Readiness for Inclusion in Certification 24 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H HL7 Implementation Guide for CDA © Release 2: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, Release 1 § (f)(4) – Transmission to cancer registries IHE Quality, Research, and Public Health Technical Framework Supplement, Structured Data Capture, Trial Implementation § (f)(5) – Transmission to public health agencies – case reporting

Standards Readiness for Inclusion in Certification 25 Standard Certification Criteria in Proposed Rule Maturity L/M/H Adoptability L/M/H HL7 Implementation Guide for CDA ® Release 2 – Level 3: Healthcare Associated Infection Reports, Release 1, U.S. Realm § (f)(6) – Transmission to public health agencies – antimicrobial use and resistance reporting HL7 Implementation Guide for CDA Release 2: National Health Care Surveys (NHCS), Release 1 – US Realm, Draft Standard for Trial Use § (f)(7) – Transmission to public health agencies – health care surveys

Standards Prioritization Standards Ready for Prime Time: Standards not ready for prime time: Might be ready: 26

General Themes 27 More attention should be paid to the broader range of standards and requirements essential to learning health system objectives. – Many HIT systems that support research and many clinical activities currently use other standards that might not transition or interoperate well. The Certification Program should allow for versioning of standardized terminologies without changes in regulation. – It is preferable to specify the floor, rather than the ceiling – Specific codes should not be identified in regulation The NPRM should support methods for combining use of LOINC and SNOMED that are consistent with current published cooperation agreements – Cooperation Agreement July 2013 Between The International Health Terminology Standards Development Organisation (IHTSDO) and The Regenstrief Institute, Incorporated (RII). – In general use LOINC for the question and SNOMED CT for the answers unless there is a good reason not to. The Common Clinical Data Set needs further vetting. – The Common data set items should align with Clinical Data Acquisition Standards Harmonization (CDASH) as closely as possible. NPRM should avoid regulation that depend on action by entities outside the regulator’s control such as specifying “pending” codes.

Workgroup Assignments 28 Group 1Members Pharmacogentics Data – Standards Question, p.239 There are existing or developing standards applicable to the capture, storage, display, and exchange of potentially clinically relevant genomic data, including the pharmacogenomic subset Common Clinical Data Set Definition - vocabulary standards p.246 National Drug Codes for Administered Vaccinations, p.170 Transmission to Public Health Agencies – all sections, p.176 Immunization History and Forecast, p.174 John Carter (lead) Todd Cooper Jamie Ferguson (co-chair) Margaret Haber Stan Huff Mitra Rocca John Speakman

Group 1 29 Pharmacogenomics Data – StandardsPharmacogenomics Data – Standards p. 239 The pharmacogenomics domain in the CDISC Study Data Tabulation Model (STDM) standard should be considered. P. 237: Pharmacogenomics data is being included in an increasing number of FDA-approved drug labels. Recommend leveraging HL7 Structured Product Labeling (SPL) standard for inclusion of pharmacogenomics data. A natural area of focus for needed standards development should be in future versions of SPL Pharmacogenomics standards developed through CDISC for research and the Life Sciences Domain Analysis of the NCI should be considered as sources. Common Clinical Data Set Definition - Vocabulary Standards Common Clinical Data Set Definition - Vocabulary Standards p. 246 The Common Clinical Data Set needs further vetting and harmonization, especially among federal agencies. The Common data set items should align with Clinical Data Acquisition Standards Harmonization (CDASH) as closely as possible. Specific versions of vocabulary standards specified may become obsolete or superseded and systems that are able to use later versions should be allowed to do so. Workgroup members would like to see source of truth on each item in the common clinical data set and its associated vocabulary (e.g., a table) An effort should be made to align the Common Clinical Data Set with the Core Common Dataset (~ 200 elements) that is recommended by FDA and paves the way to standards required by FDA and a learning health system

Group 1 30 National Drug Codes for Administered Vaccinations National Drug Codes for Administered Vaccinations p Disagree with replacing CVX with NDC because CVX is specifically useful for coding instances when the and recommend augmenting records to include NDC with CVX for specific use cases. CVX is used for times when the precise manufacturer and package are not known and not needed as in shot records. 2.Support the use of NDCs to augment CVX. CVX should not be replaced by NDC § (f)(2) (Transmission to public health agencies – syndromic surveillance) § (f)(2) (Transmission to public health agencies – syndromic surveillance) p. 176 Assuming that UCUM is not precluded based on our reading of the implementation guide we believe the proposed rule is acceptable § (f)(3) (Transmission to public health agencies – reportable laboratory tests and values/results) § (f)(3) (Transmission to public health agencies – reportable laboratory tests and values/results) p. 179 Agree, as long as Unified Code for Units of Measures (UCUM) is not precluded. Immunization History and Forecast Immunization History and Forecast p. 174 CVX codes exist to support documentation of immunization when manufacturer, package, and lot number are not known or needed, such as in a shot record. We disagree with replacing CVX with NDC and support the ability to augment the CVX with the NDC when information is available and needed.

Workgroup Assignments 31 Group 2Members Family health history, p.16 “Minimum Standards” Code Sets, p.32 Object Identifiers (OIDs) for Certain Code Systems, p.32 Demographics, p.44 Vital Signs, Body Mass Index (BMI), and Growth Charts, p.49 Smoking status, p.67 Social, Psychological, and Behavioral Data, p.81 Work Information – Industry/Occupation Data, p.89 U.S. Uniformed/Military Service Data, p.92 Encounter Diagnoses, p.105 Medication Dosing, p.118 Eric Rose (lead) Steven Brown Betsy Humphreys Rosemary Kennedy Becky Kush (co-chair) Harry Rhodes Asif Syed The Common Dataset should be aligned and harmonized across Federal Agencies

Group 2 32 § (a)(14) Family health history § (a)(14) Family health history p. 68 1) § (a)(4): The NPRM text should indicate that both SCT-International plus the US Extension are included in the US Edition of SNOMED CT distributed by the National Library of Medicine. 2) The phrase “in accordance with” is ambiguous and should be clarified. In particular, it would be advisable to clarify that use of an interface terminology mapped to the referenced standard for recording data constitutes recording of the data “in accordance with” the standard. At this time it may be overreaching to require the HL7 Pedigree standard. “Minimum Standards” Code Sets p. 32“Minimum Standards” Code Sets “If adopted, a newer version of a minimum standards code set would serve as the baseline for certification. As with all adopted minimum standards code sets, health IT can be certified to newer versions of the adopted baseline version minimum standards code sets for purposes of certification, unless the Secretary specifically prohibits the use of a newer version (see § and 77 FR 54268).”77 FR  Agree the Certification Program should allow for versioning of standards without requiring changes in regulation.

Group 2 33 § (a)(5) Demographics § (a)(5) Demographics p. 44 It would be valuable if there was harmonization of demographic data across federal agencies. Since the prior requirement for CEHRT was to use the simpler OMB standard, adopting the CDC standard would require re-collection of data from all patients. The CDC race list* is long, and may be confusing in use. * Preamble proposes, “health IT developers and health care providers would work together to establish the appropriate implementation given the care setting.” This could result in user interfaces with poor usability, which in turn could affect the accuracy of data collection. Requirement that CEHRT be “able to aggregate each one of a patient's races and ethnicities to the categories in the OMB standard for race and ethnicity” If the CDC race code list is adopted, then transformation of the CDC-encoded race data to the OMB standard would more suitable for downstream analytical systems. Object Identifiers (OIDs) for Certain Code Systems Object Identifiers (OIDs) for Certain Code Systems p. 32 The Object Identifiers (OIDs) p.32 are consistent with the OIDS identified in the National Library of Medicine Value Set Authority Center (VSAC).

Group 2 34 § (a)(6) Vital signs, body mass index, and growth charts § (a)(6) Vital signs, body mass index, and growth charts p. 49 Re: vital signs measurements that may be calculated based on other vital signs measurements Should explicitly state that if a CEHRT provides the capability to calculate these values, it need not provide the ability to directly enter them (superfluous and introduce the possibility of error). Re: The stipulation of specific LOINCs Avoid identifying specific LOINC codes for storage of vital signs (or any data). LOINC codes may be updated or deprecated by the publishers of LOINC Specific LOINCs listed are unduly restrictive since other, more specific, LOINCs exist that are pre-coordinated with relevant details Restricting specific LOINC codes to a more granular level could potentially discard critical clinical information Measurements are not semantically identical, and to promote admixture of instance data as if they are (which would be the effect of the regulation as written) would potentially be detrimental to patient care Re: The requirement to record date of birth and sex along with BMI percentile, weight for length, and occipital-frontal circumference. Seems redundant, as recording of sex and DOB would be part of the demographic recording function of the EHR and would generally be performed one time only for every patient. It seems to imply that this data should be captured separately for each instance where BMI percentile is calculated, which would be unnecessary and superfluous. Re: Weight for length-It seems that this is likely to reflect weight for length percentile. Re: “measuring- or authoring-type source of the vital sign measurement”-Should ideally be standardized (SNOMED has some codes that would be applicable, e.g. for type of sphygmomanometer; Might need to be built out in some areas e.g. source of information).

Group 2 35 § (a)(12) Smoking status § (a)(12) Smoking status p.67 Laudable to liberalize the use of SNOMED CT codes to represent smoking status beyond the 8 codes used for 2014 edition certification criteria Problem that only those 8 codes are permissible for representing smoking status in the Common Clinical Data Set and for electronic transmission in a summary care record. The premise that any other smoking status code could be mapped to one of those 8 (as stated in the preamble) is erroneous. o Example: For instance, SNOMED , “trivial cigarette smoker (less than one cigarette/day)” is not a child, in the SNOMED hierarchy, of any of the 8 smoking-related codes required in the 2014 edition certification rule. Clarify that this refers to tobacco smoking status, rather than information on the smoking of other substances, since the intent of this criterion appears to be tobacco-specific. The Committee recommended a different and shorter (2 questions) measure for tobacco use and exposure than the one previously established as the standard for EHR certification. Shorter seems better, even if it requires making a change

Group 2 36 § (a)(21) Social, psychological, and behavioral data § (a)(21) Social, psychological, and behavioral data p.81 Valuable to be able to capture psychosocial and behavioral data in EHRs in structured and coded form. The proposal to encode “answer” data should be rethought, generally not in the semantic scope of LOINC o SNOMED “qualifier value” hierarchy does cover this semantic area o Commonly used in other similar use cases o For the “questions”, however, e.g. “highest level of education completed”, LOINC would certainly be appropriate Regulation should not be based on any premises of action by entities outside the regulator’s control o If NRPM refers to a “pending” code, should have publicly available assurances from the SDO that the code will be release The ability to record gender identity separate from biological sex is important and its inclusion is laudable. Regarding sexual orientation - allow any SNOMED code describing sexual orientation to be used instead of limiting to 3 specific SNOMED coded The list of specific data required probably exceeds what is needed (e.g. increasing knowledge of, and reducing, health and health care disparities based on psychosocial parameters) o Example: capture how many times a week someone talks by phone with family, friends, and neighbors Add o Dietary habits o Use of psychoactive substances other than alcohol and nicotine

Group 2 37 Work Information – Industry/Occupation Data Work Information – Industry/Occupation Data pp Use of SNOMED CT for encoding occupation should be given strong consideration o Contains 3,750 distinct codes for occupation o Already well-established as a health care terminology for use in CEHRT o May be less overhead in its adoption for encoding occupation data. o Its hierarchical structure facilitates its use for reporting, decision support, and other uses that rely on logic that groups together similar concepts. o SNOMED would facilitate easily identifying all patients who are healthcare professionals, (e.g. to make sure they have been vaccinated for hepatitis B or get annual screening for tuberculosis) Options o Analyze SNOMED CT for gaps vis-à-vis other preferred lists like the CDC occupation list and propose addition of any cap concepts to SNOMED CT US Extension o Cross-map SNOMED occupation codes with the CDC’s occupation codes to allow analysis that combines data encoded in both

Group 2 38 U.S. Uniformed/Military Service Data U.S. Uniformed/Military Service Data p. 92 SNOMED CT contains o A sub-hierarchy “military personnel” within the “occupation” hierarchy o Codes to represent particular characteristics of uniformed service that may be relevant to future health risks, e.g. “exposure to combat” (SNOMED ). Encounter Diagnoses Encounter Diagnoses p. 105 No comment Medication Dosing Medication Dosing p. 118 The NPRM proposes to require that CEHRT “be capable of limiting a user's ability to electronically prescribe all medications in only the metric standard”. Metric units do not apply to all medication dosage forms. Topical medications are often by necessity imprecise (e.g., apply lightly to affected areas twice daily), By necessity use non-metric units (e.g. eye drops, where the dosage will be in terms of number of drops, or inhalers, will the dosage will be in puffs) Per the preamble, the intent of this criterion is to apply to oral liquids, so revising the text to indicate that would address this issue.