Difference between revisions of "Results Synchronization"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
== Results Synchronization, BW Steps 83-88 ==
+
== RID-RCD Results Synchronization==
  
 +
The Results Concept Dictionary (RCD) is an Allscripts list of common resultables returned on lab results. This would be a list of items such as White Blood Count (WBC), Hemoglobin, or Platelets. Mapping resultables to the RCD currently provides no benefit. This is a feature that will be used in the future. (RID-RCD mapping is not required or part of Results Synchronization so should this be separate).
  
−
The Results Concept Dictionary (RCD) is an Allscripts list of common resultables returned on lab results. This would be a list of items such as White Blood Count (WBC), Hemoglobin, or Platelets. Mapping Resultables to the RCD currently provides no benefit. This is a feature that will be used in the future.
+
The one place within the application that Results mapping/synchronization has an impact is when displaying flowsheets in the application.  Equivilent results that are not synched will display as separate rows on flowsheets. Sycnronizing resultables and mapping the RID to the RCD is a large work effort.  As an alternative, the ’’Results flowsheet equivalents’’ feature can be used to ensure that results for the same resultable item that flow into the application from different vendors appear on the same line in flowsheets.
−
 
 
−
The one place within the application that Results mapping/synchronization has an impact is when displaying flowsheets in the application.  Equivilent results that are not synched will display as seperate rows on flowsheets. Sycnronizing resultables and Mapping the RID to the RCD is a large work effort.  As an alternative, the ’’Results flowsheet equivalents’’ feature can be used to ensure that results for the same resultable item that flow into the application from different vendors appear on the same line in flowsheets.
 
  
 
We recommend that during an upgrade the '''Results flowsheets equivalents''' task be completed and that the RID/RCD mapping can be done at a later date when doing so will add more functionality to the application.
 
We recommend that during an upgrade the '''Results flowsheets equivalents''' task be completed and that the RID/RCD mapping can be done at a later date when doing so will add more functionality to the application.
  
−
=='''Results Flowsheets Equivalents'''==
+
==Results Flowsheets Equivalents==
  
 
*From the Physician Admin Workspace, navigate to the flowsheets menu.
 
*From the Physician Admin Workspace, navigate to the flowsheets menu.
Line 18: Line 17:
 
*Within this window select all of the resultable items that should be considered equivalent for the flowsheets.
 
*Within this window select all of the resultable items that should be considered equivalent for the flowsheets.
  
−
==Results Synchronization==
+
Note: As new flowsheets are created this "Results Flowsheets Equivalents" task will need to be performed for each resultable. The "Results Flowsheets Equivalents" task does not need to be completed if the organization chooses to do the full RID synchronization instead.
−
 
 
−
 
 
−
'''If you are doing the synchronization for Results, make sure to tell the UC/Interface Tech as the Interfaces will need to be updated after mapping/synchronization occurs'''
 
−
*Identify the (resultable?) items that you are currenly using in flowsheets.
 
−
*From the Physician Admin Workspace, navigate to the flowsheets menu.
 
−
**Identify the orderable items that are used in flowsheets in your setting.
 
−
**Identify the corresponding resultable items that correspond to those orderable items.
 
−
 
 
−
==Build the RID Dictionary for the primary vendor==
 
−
The [[Results Item Dictionary]] (RID) is the dictionary that houses the actual dictionary items for the returned result data.  These are the place holders for the numeric or text values that are returned by the vendor.  For example if you order a CBC that would include resultable such as White Blood Count (WBC), Red Blood count (RBC), or Hemoglobin counts. 
 
−
 
 
−
This exercise requires you to link the resultables to the parent order for the primary results only.
 
−
 
 
−
If you are unfamiliar with the [[SSMT]] columns for the RID spreadsheet please refer to [[SSMT:  RID - Resultable Item Dictionary]]
 
−
 
 
−
== Link the secondary vendor to the primary==
 
−
This step is the first part of the synchronization process.  This will allow you to enter identical labs from multiple vendors but only presents the user with one option.  For example if you are loading LabCorp and Quest Orders, they would both have a CBC.  If you don't sync the Orders, the user would have two CBC's to choose from and it would be confusing.  When the two have been linked, the user will simply choose the requested performing location and it would then be routed appropriately with the correct codes.  The requested performing location can be defaulted in many ways in v11.  You can set them based on site, insurance, or a combination of the two.  This allows you to define the most likely choice, but also allows the user to change it if they have feel it needs to go elsewhere.
 
−
 
 
−
In this exercise you need to tell the system which secondary labs are equivalent to the primary labs.  In some cases, the primary vendor may have multiple codes for the same Orderable as well.  In that case, you would treat the duplicate orderable as if it were a secondary lab also.  The primary value should be the active Order code.  This is done in the order Performing Facility Identifiers spreadsheet. 
 
−
 
 
−
If you are unfamiliar with this spreadsheet, please refer to [[SSMT:  Order Performing Facility Identifiers]]
 
−
 
 
−
If your secondary lab has orders that do not match your primary vendors entries, you would enter that order as if it were the primary lab and complete Steps 3 and 4 for that Order.
 
−
 
 
−
==Link your secondary lab results to the primary==
 
−
This step is optional, but recommended.  This wasn't available in v10, but the advantage of synchronizing resultables for multiple vendors is that it allows the user to flow common results from multiple vendors on one line.  This is a huge benefit to the providers if they want to track the trend of a results ordered from multiple places. 
 
−
 
 
−
This step is very similar to the Order synchronization process.  You will fill out the Results Where Performed Identifiers spreadsheet to complete this process. 
 
−
 
 
−
If you are unfamiliar with this spreadsheet, please refer to [[SSMT:  Results Where Performed Identifiers]]
 
−
 
 
−
If your secondary vendor has items that can't be matched to the primary vendor, you should load the item into the RID dictionary by following step 4.  This is a little trickier than the first pass because you may have to place the secondary labs result items under the primary labs order code.  If the secondary labs order is tied to a primary lab in the Order Performing Facility Identifier spreadsheet, you must load the unlinkable secondary resultables under the primary labs order code in the RID.
 
−
 
 
−
Let's continue the example using LabCorp as your primary and Quest as your secondary.  Imagine that the LabCorp CBC included only WBC and RBC, but the Quest CBC had WBC, RBC, and MCH.  You wouldn't be able to synchronize MCH because it doesn't exist in the Primary lab, but the result is under an Order Code (CBC) that is synchronized.  In that case you would need to load the Quest MCH resultable code into the RID spreadsheet tied to the LabCorp CBC Order code.
 

Latest revision as of 11:43, 19 July 2013

RID-RCD Results Synchronization

The Results Concept Dictionary (RCD) is an Allscripts list of common resultables returned on lab results. This would be a list of items such as White Blood Count (WBC), Hemoglobin, or Platelets. Mapping resultables to the RCD currently provides no benefit. This is a feature that will be used in the future. (RID-RCD mapping is not required or part of Results Synchronization so should this be separate).

The one place within the application that Results mapping/synchronization has an impact is when displaying flowsheets in the application. Equivilent results that are not synched will display as separate rows on flowsheets. Sycnronizing resultables and mapping the RID to the RCD is a large work effort. As an alternative, the ’’Results flowsheet equivalents’’ feature can be used to ensure that results for the same resultable item that flow into the application from different vendors appear on the same line in flowsheets.

We recommend that during an upgrade the Results flowsheets equivalents task be completed and that the RID/RCD mapping can be done at a later date when doing so will add more functionality to the application.

Results Flowsheets Equivalents

  • From the Physician Admin Workspace, navigate to the flowsheets menu.
  • Copy down the resultable items that are used in each flowsheet.
  • From the TWAdmin workspace navigate to dictionaries
  • Select the Resultable Item Dictionary
  • Highlight the Resultable Item that you are using for flowsheets
  • In the detail section of the resultable item, click on the blue link titled Considered equivalent only for flowsheet graph
  • Within this window select all of the resultable items that should be considered equivalent for the flowsheets.

Note: As new flowsheets are created this "Results Flowsheets Equivalents" task will need to be performed for each resultable. The "Results Flowsheets Equivalents" task does not need to be completed if the organization chooses to do the full RID synchronization instead.

Retrieved from "https://wiki.galenhealthcare.com/index.php?title=Results_Synchronization&oldid=16532"