Covered by this topic
This document is intended to describe and assist users with the process to validate discrete observations imported from another system.
- 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 .
Validate the discrete values imported to Enterprise Health , listed in the table below.
|Name of observation to validate
|Expected result of observation being validated
Validation Instructions (video )
Log into the Enterprise Health system.
Navigate to the Quick View , and using the portlet, perform a Chart Search for a record from the list of 8-10 charts.
- Select the preferred search criteria, such as D.O.B., Name, or EMP # (sometimes referred to as Medical Record Number, or MR#).
- Type in the appropriate value and click Search, or press enter. (For more information and instructions on searching, see Basic Initial System Information or Detailed Searching in E-Chart .)
Verify the chart. Demographic data (e.g., Name, Status, MR#) is displayed on the Patient Header.
Select Observations/Flowsheets from the Medical Record chart tab.
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.
Observation names are displayed alphabetically, by default, with all data listed horizontally across the page.
To aid in validation and instead view data vertically, or with dates descending, simply click the Vertical radio button before clicking Search. The results will be displayed with the dates in the first column, with the results listed across the page. (See our help documentation for more detailed information on the Observations Tab .)
Within each chart, it is possible a Flowsheet of logically grouped observations may exist. 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.
- 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.
- Using the Validation Tracking Template , record any discrepancies or differences.
- Take screenshots of each system, highlighting the differences found. (Remember: DO NOT email PHI)
- Contact Enterprise Health with the findings.
Navigate to the Reports sidemenu.
Select the Visits report list.
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.
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.