eScription issue

[Michael Hertel]

We are in the process of implementing eScription.

Our latest challenge (among many) is that many of the dictated notes are not visit/encounter related. If the notes are not transcribed on a visit number, then they will be held and not interface outbound to our EMR. I am being asked to create a dummy visit number (TR$MRN) to be placed in each ADT transaction going to eScription that has a null visit number. This is wrong on so many levels  😕 I’m wondering how others are handling this.

Topic

[Chris Williams]

Depends a lot on what EMR you are using. We’re doing eScription with Epic if that would help.

[Highland Dave]

we are in the process of implementing eScription to Epic.  One of our issues is eScription will send the same provider info in TXA-9 & TXA-10.  Epic Bridges does not care for that.  Did you encounter this and create a work around?  eScription wants to know if I check these fields and they match, can I clear out one of them.  I tried this but I believe the transcription does not post to the correct place in Epic.  We are also trying to implement partial dicatation for Epic progress notes.  Have you come across anything we should watch or catch.

[Michael Heldt]

We have the MT’s place a “T” into the visit account # in Escription.  “T” values are allow through the rules in Escription to go out the MDM interface.  In cloverleaf I remove any visit id’s that are not numeric.  The trans/gen tables in epic are setup (for particular worktypes) to create an encounter.  Letters would be an example.

For a short period of time during testing we too had the same provider id being sent in txa 9 and txa 10..which as you note epic does not like. I asked escription to take care of that and they did.  It started when we were trying to get the “resident/non authorizing” tested.

We don’t do partilar dictations necessarily.   If the same job crosses and the document is not signed, it gets updated.  The chart review is setup in epic display a hyperlink to that “version” of that document.  We aren’t doing “parent/child” (TXA 12.3 TXA 13) for escription since I was told from escription that they have no way of tell if the document has been updated vs created.

If you have multiple contributor systems that send in MDM messages (example: multiple transcription systems) the TXA 12.3 value is handled globally in Epic.  So we have to make it “unique” in cloverleaf for each system.

[Author]

Replies