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

Comments. A couple of commenters stated that the prescribing capabilities must allow for weight-based dosing calculation with intelligent rounding and that without this, e-prescribing will not be helpful to pediatricians. Response. We recognize that this is an important capability for pediatricians; however, we do not believe that it necessary to require it as a condition of certification at the present time. Again, this does not preclude Complete EHR and EHR Module developers from including this capability. Comments. A few commenters expressed concerns about some pharmacies not being capable of receiving electronic prescriptions which they stated could cause a negative impact on the workflow. One commenter suggested that we add a “where possible” to the certification criterion. Response. While we recognize that some pharmacies may be unable to receive electronic prescriptions at the present time, we do not believe this limitation should affect the capability that Certified EHR Technology must provide. Further, we do not believe that inserting “where applicable” would be beneficial because it would make the criterion unnecessarily ambiguous. This phrase would relate to when electronic prescribing should be conducted, not how it should be done, which is the focus of this certification criterion. Comment. A commenter stated that the electronic prescribing process should be linked to the contraindication and formulary conflict process and should provide automatic alerts. Another commenter recommended that information relating to the language the patient speaks should be required as part of the electronic prescribing process, so that pharmacy is notified of a patient’s need for language assistance. Page 134 of 228

Response. We do not believe that it would be appropriate to expand the certification criterion as suggested at this time. This does not preclude a Complete EHR or EHR Module developer from pursuing other ways to optimize how a Complete EHR or EHR Module may function. §170.304(c) - Record demographics Meaningful Use Stage 1 Objective Record demographics • preferred language • gender • race • ethnicity • date of birth Meaningful Use Stage 1 Measure More than 50% 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 demographics recorded as structured data Page 135 of 228 Certification Criterion Interim Final Rule Text: Enable a user to electronically record, modify, and retrieve patient demographic data including preferred language, insurance type, gender, race, ethnicity, and date of birth. Final Rule Text: §170.304(c) Record demographics. Enable a user to electronically record, modify, and retrieve patient demographic data including preferred language, gender, race, ethnicity, and date of birth. Enable race and ethnicity to be recorded in accordance with the standard specified at 170.207(f). Comments. Several commenters recommended that we adopt the OMB race and ethnicity codes. Response. We agree with these commenters and have adopted the OMB race and ethnicity codes. In the Medicare and Medicaid EHR Incentive Programs proposed rule (75 FR 1855), CMS stated that race and ethnicity codes should follow current Federal standards. We note that the OMB race and ethnicity codes constitute a government- unique standard for the purposes of the National Technology Transfer and Advancement Act of 1995 (NTTAA). We have adopted this standard because it provides an easily understood structure and format for electronically transmitting the data elements identified in the meaningful use Stage 1 objective, the standard is readily available, in general it provides the best standard to use to support our policies goals. Moreover, we

Response. We do not believe that it would be appropriate to expand the<br />

<strong>certification</strong> criterion as suggested at this time. This does not preclude a Complete EHR<br />

or EHR Module developer from pursuing other ways to optimize how a Complete EHR<br />

or EHR Module may function.<br />

§170.304(c) - Record demographics<br />

Meaningful Use<br />

Stage 1<br />

Objective<br />

Record<br />

demographics<br />

• preferred<br />

language<br />

• gender<br />

• race<br />

• ethnicity<br />

• date <strong>of</strong> birth<br />

Meaningful Use Stage<br />

1 Measure<br />

More than 50% <strong>of</strong> all<br />

unique patients seen by<br />

the EP or admitted to<br />

the eligible hospital’s or<br />

CAH’s inpatient or<br />

emergency department<br />

(POS 21 or 23) have<br />

demographics recorded<br />

as structured data<br />

Page 135 <strong>of</strong> 228<br />

Certification Criterion<br />

Interim Final Rule Text:<br />

Enable a user to electronically record, modify, and<br />

retrieve patient demographic data including preferred<br />

language, insurance type, gender, race, ethnicity, and date<br />

<strong>of</strong> birth.<br />

Final Rule Text:<br />

§170.304(c)<br />

Record demographics. Enable a user to electronically<br />

record, modify, and retrieve patient demographic data<br />

including preferred language, gender, race, ethnicity, and<br />

date <strong>of</strong> birth. Enable race and ethnicity to be recorded in<br />

accordance with the standard specified at 170.207(f).<br />

Comments. Several commenters recommended that we adopt the OMB race and<br />

ethnicity codes.<br />

Response. We agree with these commenters and have adopted the OMB race and<br />

ethnicity codes. In the Medicare and Medicaid EHR Incentive Programs proposed rule<br />

(75 FR 1855), CMS stated that race and ethnicity codes should follow current Federal<br />

standards. We note that the OMB race and ethnicity codes constitute a government-<br />

unique standard for the purposes <strong>of</strong> the National Technology Transfer and Advancement<br />

Act <strong>of</strong> 1995 (NTTAA). We have adopted this standard because it provides an easily<br />

understood structure and format for electronically transmitting the data elements<br />

identified in the meaningful use Stage 1 objective, the standard is readily available, in<br />

general it provides the best standard to use to support our policies goals. Moreover, we

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

Saved successfully!

Ooh no, something went wrong!