11.2 Warehouse Data Mapping: Data Mapping Workbook
The purpose of this mapping is to map a client’s custom dictionary entries to values that are used by CQS in order to calculate properly for Meaningful Use. This mapping does not change any values within the client’s system. As the data from the client’s system is uploaded to the Allscripts Data Warehouse the information will be processed according to the mapping and then calculated for Meaningful Use. This process is required for all client's upgrading to Allscripts Enterprise EHR v11.2. Clients will need to complete the Data Mapping Workbook regardless if they currently use on premise CQS or plan on implementing the Basic Clinical Quality Reporting functionality included with the Stimulus Set contract.
Example: For gender, CQS lists the following genders:
If a client was to use Boy and Girl as genders, then these entries would not be calculated. By performing the Data Mapping the client can then map the entry of Boy to Male and the entry of Girl to Female. Once mapped, these entries will now be included in the calculation.
The workbook contains a macro that will look to automatically map these values. Any values which the workbook cannot automap will be the responsibility of the client to complete. The Upgrade Consultant will perform this automapping and hand off the workbook to the client to complete the remaining items. The Upgrade Constultant will provide the client with predefined definitions to help in the process. Once the workbook has been completed, the client should return it to the Upgrade Consultant.
Data Mapping v1.19
* Appointment Types only need to by mapped when one of more providers using AEEHR do NOT use the charge module
When calculating Meaningful Use objectives, some of the objectives count the number of Encounters (for example - Clinical Summary), while some measure the number of patients during the reporting period (for example - Demographics and BMI). If a group has any providers intending to report Meaningful Use that are not on the Charge module, they will need to map Appointment Types so that the Stimulus Set Reports recognize the nature of the appointment. There are many Appointment Types that would never be recognized for reporting and normally that is determined by the CPT code. When Charge is not in use, this mapping enables the Stim Set reports to recognize the type of appointment and whether or not it will be used for reporting. Recommendation: Map all Appointment Types regardless of using Charge. It takes a little effort, but in the event it is ever necessary in the future, it will be done.
Appointment Type Exclusion?
* Result Type only need to be mapped for 1) the Results that are associated to the chosen CQM and 2) the LOINC code is not assigned
After selecting CQM, a key build task is assigning the correct LOINC codes to the Results that are being reported on. If the AEEHR group does not have these LOINC codes assigned, they can choose to map the Result Types that are associated to the the CQM.
Recommendation: Map all Result Types. Like Appointment Type, it take some effort up front, but will reduce the work required in the future if it ever becomes a required process.