Observations Validation Test Script

This document is intended to describe and assist users with the process to validate discrete observations imported from another system.

Requirements

• Compile a list of 8-10 different charts containing individual observations from the legacy/existing system. Ensure the examples include varied complexity and multiple years of data to address potential import discrepancies that could arise.
• Multiple monitors are recommended to assist with comparing legacy data to the data imported to Enterprise Health .

Data Fields 

Validate the discrete values imported to Enterprise Health , listed in the table below. 

Field Name	Description	Example
Employee ID	Employee Identifier	MR 12345
Observation Name	Name of observation to validate	p.work_phone
Observation Result	Expected result of observation being validated	8883139766

Validation Instructions (video )

1. Log into the Enterprise Health system.

2. Navigate to the Quick View , and using the portlet, perform a Chart Search for a record from the list of 8-10 charts.

   

1. Verify the chart. Demographic data (e.g., Name, Status, MR#) is displayed on the Patient Header.

2. Select Observations/Flowsheets from the Medical Record chart tab.

   

3. The Observations Search will display. Simply click the Search button to search all observations, unless the search needs to be more specific or filtered down.

1. With the observations displayed, begin comparing the data. Toggle between the legacy system and the Enterprise Health system to validate the data. If access to the legacy system is unavailable, users may use the CSV file presented to Enterprise Health for initial import. 

1. Using the [Validation Tracking Template](https://docs.google.com/spreadsheets/d/1FRV_L_J38dhBDi13elXHVJddMuIZy6Sq5P3Viv9IXxE/edit#gid=0), record any discrepancies or differences. 2. Take screenshots of each system, highlighting the differences found. (Remember: DO NOT email PHI) 3. Contact Enterprise Health with the findings.

Reports (video ) The Patient Observations report is particularly helpful in validating data between systems. To access and utilize this report:

1. Navigate to the Reports sidemenu.

2. Select the Visits report list.

   

3. Criteria may be added to filter or drill down data. The Entered By field, for example, can be used to further refine the results. The Entered By value when performing a data migration is typically Import User. Otherwise, the legacy system name may be used, or a meaningful acronym (e.g., Cerner Import, OHM Import) may be chosen. 

   

FAQs

Q: I am only validating specific observations. Is there a way to filter to just the ones I need? A: Yes. Users may use the Patient Observations Report , described above , to search specific observation values. Otherwise, it is possible a Flowsheet  of logically grouped observations may exist within each chart. A Flowsheet is a grouping of observations, such as Vitals, Glucose levels, Questionnaire responses, etc. If a flowsheet is available, select it from the Flowsheet drop-down to load the results.

Q: Why are some observations only listed once, even though they apply across all dates (e.g., Race, Ethnicity, Email, etc.)? A: Once an observation is recorded, it is not repeated as a duplicate discrete value. If the observation changes, then a new observation will display with the observation history always available. WARNING: Users with proper security permissions may Delete observations, along with their history. Q: Can I create my own flowsheets with just the observations I need to validate? A: This depends on company policy and is controlled through user security settings. If permitted, select users may create flowsheets, as needed.