ehr onc final certification - Department of Health Care Services

ehr onc final certification - Department of Health Care Services ehr onc final certification - Department of Health Care Services

dhss.alaska.gov
from dhss.alaska.gov More from this publisher
10.08.2013 Views

Comment. A commenter recommended that “drug-test checks” should be added. The commenter stated that many drugs require some form of laboratory testing to ensure that drugs are prescribed appropriately. The commenter stated, for example, that an anticoagulant medication should not be prescribed unless there is a test result on record that shows that giving this drug would not cause harm. Response. Presently, drug-test checking is not a required capability for eligible professionals and eligible hospitals to use in order to successfully meet the requirements of meaningful use Stage 1. Accordingly, we do not believe that it would be appropriate to require Certified EHR Technology to be capable of performing drug-test checks as a condition of certification at the present time. §170.302(b) - Maintain up-to-date problem list Meaningful Use Stage 1 Objective Maintain an up-todate problem list of current and active diagnoses Meaningful Use Stage 1 Measure More than 80% of all unique patients seen by the EP or admitted to the eligible hospital’s or CAH’s inpatient or emergency department (POS 21 or 23) have at least one entry or an indication that no problems are known for the patient recorded as structured data Page 54 of 228 Certification Criterion Interim Final Rule Text: Maintain up-to-date problem list. Enable a user to electronically record, modify, and retrieve a patient’s problem list for longitudinal care in accordance with: (1) The standard specified in §170.205(a)(2)(i)(A); or (2) At a minimum, the version of the standard specified in §170.205(a)(2)(i)(B). Final Rule Text: §170.302(c) Final rule text remains the same as Interim Final Rule text, except for references to adopted standards, which have been changed. Comments. Several commenters expressed concerns about the use of ICD-9-CM because it is primarily used for billing and administrative purposes and may not accurately represent the true clinical meaning of a problem or condition when it is documented at the point of care. One commenter stated a concern that the problem list standards do not allow for capturing of free text that health care providers use when an appropriate code is in neither SNOMED-CT® nor ICD-9-CM.

Response. The comments are correct in that ICD-9-CM is primarily used for billing and administrative purposes. SNOMED-CT® is offered as an alternative standard that will support more clinical descriptions of patient problems or conditions. We believe that with the adoption of both SNOMED-CT® and ICD-9-CM, healthcare providers should have adequate coverage for patient diagnoses and conditions. We are discouraging the use of free text for documenting problem lists since this will limit the usefulness of problem lists for clinical reminders, decision support and other patient safety and quality reporting. Comments. Several commenters recommended that only SNOMED-CT® be adopted, or alternatively, that we expressly indicate an intention to move away from ICD- 9CM and ICD-10 in the future. Another commenter recommended against the adoption of SNOMED-CT® because the commenter felt that our adoption of SNOMED-CT® would require eligible professionals and eligible hospitals to use both ICD-9-CM and SNOMED-CT®. One commenter recommended that a publicly vetted and HHS approved standard mapping between ICD-9-CM and SNOMED CT® should be made available at the public’s expense. Response. We agree conceptually that a single standard for clinical information would be desirable in the long term. However, presently both ICD-9-CM and SNOMED- CT® are used by EHR technology to code clinical information, and adopting both would provide users with additional flexibility. Moreover, we anticipate that as meaningful use objectives and measures evolve over time, we will receive additional public input and experience related to these standards and may eventually be able to adopt only one standard. Page 55 of 228

Response. The comments are correct in that ICD-9-CM is primarily used for<br />

billing and administrative purposes. SNOMED-CT® is <strong>of</strong>fered as an alternative standard<br />

that will support more clinical descriptions <strong>of</strong> patient problems or conditions. We believe<br />

that with the adoption <strong>of</strong> both SNOMED-CT® and ICD-9-CM, healthcare providers<br />

should have adequate coverage for patient diagnoses and conditions. We are discouraging<br />

the use <strong>of</strong> free text for documenting problem lists since this will limit the usefulness <strong>of</strong><br />

problem lists for clinical reminders, decision support and other patient safety and quality<br />

reporting.<br />

Comments. Several commenters recommended that only SNOMED-CT® be<br />

adopted, or alternatively, that we expressly indicate an intention to move away from ICD-<br />

9CM and ICD-10 in the future. Another commenter recommended against the adoption<br />

<strong>of</strong> SNOMED-CT® because the commenter felt that our adoption <strong>of</strong> SNOMED-CT®<br />

would require eligible pr<strong>of</strong>essionals and eligible hospitals to use both ICD-9-CM and<br />

SNOMED-CT®. One commenter recommended that a publicly vetted and HHS<br />

approved standard mapping between ICD-9-CM and SNOMED CT® should be made<br />

available at the public’s expense.<br />

Response. We agree c<strong>onc</strong>eptually that a single standard for clinical information<br />

would be desirable in the long term. However, presently both ICD-9-CM and SNOMED-<br />

CT® are used by EHR technology to code clinical information, and adopting both would<br />

provide users with additional flexibility. Moreover, we anticipate that as meaningful use<br />

objectives and measures evolve over time, we will receive additional public input and<br />

experience related to these standards and may eventually be able to adopt only one<br />

standard.<br />

Page 55 <strong>of</strong> 228

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!