Difference between revisions of "Interfaced Document Encounter Matching"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
===Documents will be reconciled with encounter based upon a set of logic outlined below. Basically the logic will search for an appointment based on gradually loosening criteria and if it can't match then it will match on an Encounter (if the Date Time matches exactly), along with the other criteria outlined below. If all these options fail the document will create a document in an unnasocciated encounter.===
+
[[Category:ConnectR]]
*(A) = will match on an appointment
+
__TOC__
*(E) = will match on an encounter
+
Documents will be reconciled with encounter based upon a set of logic outlined below
 +
 
 +
Basically the logic will search for an appointment based on gradually loosening criteria and if it can't match then it will match on an Encounter (if the Date Time matches exactly), along with the other criteria outlined below. If all these options fail the document will create a document in an brand new encounter.
 +
 
 +
==Legend and Notes==
 +
*(A) = will match only on an appointment encounter (an appointment from the practice management system).
 +
*(E) = will match on an encounter (any type, including encounters created through the EHR and through interfaces)
 
* All steps assume that the Patient matches
 
* All steps assume that the Patient matches
#(A)Visit Number matches (57th parameter), Encounter Date (10th parameter) matches.
+
* References to providers on the Document matching, refer to the Scheduling/Performing Provider on existing appointments/encounters.
#(A)Author (creator of the document, 18th parameter in filedocworkstranscription) matches, Encounter DateTime(10th parameter) matches.
+
 
#(A)Encounter DateTime(10th parameter) matches, Force Provider Flag (59th parameter) = N in ConnectR.
+
==Matching==
#(A/E)Encoutner DateTime matches(10th parameter), Force Provider Flag(59th parameter) = N in ConnectR.
+
#(A) Visit Number EXT, Encounter Date and Interface Source ID match.
#(A)AuthorID matches(18th parameter) in ConnectR, Encounter Date matches(10th parameter).
+
#(A) Author and Encounter date/time matches.
#(A)Owern Id(34th parameter) matches in ConnectR, Encounter Date matches(10th parameter).
+
#(A) Encounter date/time matches and Force Provider Flag = N.
#(A)Matches strictly on Appointments that are Arr, Pen, and Rsc statuses.
+
#(A/E) Encounter date/time matches and Force Provider Flag = N.
#(A/E)Matches on any Encounter if its an Appointment that is in Arr, Pen, or Rsc statuses.
+
#(A) Author matches in ConnectR, Encounter Date matches.
 +
#(A) Owner matches in ConnectR, Encounter Date matches.
 +
#(A/E) Author matches in ConnectR, Encounter Date matches.
 +
#(A/E) Owner matches in ConnectR, Encounter Date matches.
 +
 
 +
==ConnectR Fields==
 +
 
 +
The fields mentioned above are the fields that you'll find in the FileDOCWORKSTranscription Message in ConnectR:
 +
* Encounter Date / Time: 10th parameter
 +
* Visit Number EXT: 57th parameter
 +
* Author: 18th parameter
 +
* Owner: 34th parameter
 +
* Force Provider Flag: 59th parameter

Latest revision as of 19:34, 19 June 2013

Documents will be reconciled with encounter based upon a set of logic outlined below

Basically the logic will search for an appointment based on gradually loosening criteria and if it can't match then it will match on an Encounter (if the Date Time matches exactly), along with the other criteria outlined below. If all these options fail the document will create a document in an brand new encounter.

Legend and Notes

  • (A) = will match only on an appointment encounter (an appointment from the practice management system).
  • (E) = will match on an encounter (any type, including encounters created through the EHR and through interfaces)
  • All steps assume that the Patient matches
  • References to providers on the Document matching, refer to the Scheduling/Performing Provider on existing appointments/encounters.

Matching

  1. (A) Visit Number EXT, Encounter Date and Interface Source ID match.
  2. (A) Author and Encounter date/time matches.
  3. (A) Encounter date/time matches and Force Provider Flag = N.
  4. (A/E) Encounter date/time matches and Force Provider Flag = N.
  5. (A) Author matches in ConnectR, Encounter Date matches.
  6. (A) Owner matches in ConnectR, Encounter Date matches.
  7. (A/E) Author matches in ConnectR, Encounter Date matches.
  8. (A/E) Owner matches in ConnectR, Encounter Date matches.

ConnectR Fields

The fields mentioned above are the fields that you'll find in the FileDOCWORKSTranscription Message in ConnectR:

  • Encounter Date / Time: 10th parameter
  • Visit Number EXT: 57th parameter
  • Author: 18th parameter
  • Owner: 34th parameter
  • Force Provider Flag: 59th parameter