TeleRIS middleware solution
TeleRIS middleware solution. This project highlights three unique TeleRIS capabilities:

  => Maintaining multiple patient ids and study ids for each patient and order.
  => Maintaining multiple conversational interfaces simultaneously.
  => Transforming DICOM through our partnership with DICOM Systems.

This hospital had several goals:

Basically the group wanted all the patient info, orders and PACS studies from all their outside contracts brought into their existing hospital RIS, PACS and dictation systems letting their radiologists seamlessly read studies. This would require the following functionality:





For the mammography services that the group provided to outside facilities, additional functionality was needed.



After a long search the group selected the ThinAir Data TeleRIS middleware solution.
The TeleRIS middleware solution consists of the typical TeleRIS single worklist functionality and HL7 integration capabilities and adds to it the following three features.




The resulting workflow of the system looks as follows:

=> The workflow begins when the remote facility either sends an HL7 ADT or order message to TeleRIS.

=> TeleRIS sends a specially formed HL7 message to the group੮ternal hospital Epic EMR system 屵estingᠨospital MRN for this outside facility patient.

=> The Epic system sends an HL7 ADT message providing TeleRIS with a hospital MRN for that outside facility patient. TeleRIS is now maintaining both the hospital MRN for the patient and the remote facility MRN.

=> The remote facility sends their DICOM study to the DICOM Systems broker (DSB). DCB temporarily holds the DICOM study. (For sites that do not send HL7 ADT or order messages to TeleRIS, the Epic EMR MRN 屵est鳠triggered at this point in the workflow.)


=> DCB sends an HL7 message to TeleRIS containing all the needed data from the DICOM header of the study including the facility MRN and accession.

=> Staff at the remote facility login to the TeleRIS web portal and see the order created by TeleRIS from the DICOM information. Staff validate and confirm the order in TeleRIS adding any additional needed information.

=> TeleRIS sends a specially formed HL7 message to the group੮ternal hospital GE RIS system. This message contains the Epic EMR MRN assigned to this patient earlier in the workflow not the remote facility MRN. The message also contains a valid GE RIS exam code which TeleRIS has automatically translated from the exam description selected by the remote facility staff. Each facility sees their own procedure description lists when in the TeleRIS portal.

=> The GE RIS sends a specially formed HL7 order message to TeleRIS providing a GE RIS accession number for this study. TeleRIS is now maintaining both the hospital accession number for the order and the remote facility accession number.

=> TeleRIS sends a specially formed HL7 message to DCB with the hospital MRN and accession. TeleRIS and DCB have maintained separate unique identifiers separate from MRNs and accession to keep orders in sync between our two system.

=> DCB updates the DICOM header of the remote facility೴udy with the hospital MRN and accession and forwards the study to the group੮ternal GE PACS where it matches up with the order previously created automatically in the GE RIS by the TeleRIS order message. (For the mammography workflow, DCB automatically identifies mamamography studies by modality and\or procedure description. In addition to the above, DCB forwards the mammography studies to the group੮ternal hospital Hologic mammography PACS.)

=> DCB sends message to TeleRIS when transfer of DICOM study from remote facility has finished.

=> TeleRIS notifies the GE RIS of study completion so GE RIS can send order to the group੮ternal hospital Powerscribe system and make the study available for radiologists in the group੮ternal hospital GE PACS.

=> Radiologists see there remote facilitiesﲤers in the same worklists they have always used and are able to seamlessly read these cases with the same tools and workflow they are familiar with.

=> The group੮ternal Powerscribe system sends HL7 result message to TeleRIS. TeleRIS posts the report in the portal for remote users to view. These remote users are able to find and view their patients, orders and reports using their own facility MRNs and accession numbers.

=> TeleRIS sends HL7 result messages to the remote facilities. These result messages contain the facilities﷮ MRNs and accession numbers not the Carle hospital IDs. Autoprint and auto fax distributions also occur, on facility specific letterhead again containing the facility௲iginal MRNs and accession numbers.

=> For the mammography workflow, when radiologists do annotations in the Hologic PACS, Hologic sends the annotated study to DCB. At this point in time, the study has the MRN and accession number of the group੮ternal hospital systems. DCB sends a specially formed HL7 message to TeleRIS. TeleRIS responds immediately with the a specially formed HL7 message containing the remote facility͒N and accession for this study. DCB updates the DICOM header of the study with the facility੮fo and forwards the study back to the original facility.

The middleware system achieves all these steps of receiving, acquiring, maintaining, changing and restoring MRNs and accession numbers automatically. The group੮ternal hospital staff do not have to manually register these outside patients in the hospital EMR. They do not have to manually enter the outside orders in the hospital RIS.

TeleRIS automatically emails the hospital staff when various events occur such as receipt of a STAT order from a remote facility, or failure of an order to be validated by staff within a given timeframe or failure of an order to be read by a radiologist with a given timeframe.

While the groupಡdiologists are able to do all their work within their existing hospital systems, the TeleRIS system provides a single point where the hospital staff can manage all the outside contract work. The robust, custom middleware integration has enabled a platform where the hospital can continue to grow their business seamlessly with no adverse impact on their radiologists.
thinairdata_11202014a005001.jpg
Back
ⰱ4 ThinAir Data Corp.
Whether you like or rolex replica not Rolex, can not deny that it is strong in the replica watches uk secondary market, this Rolex Daytona 6265 is rolex replica uk the Christie's online auction champion, is also numbered 1 of the auction. Before the auction, this 6265 is already one of replica watches the most watched auction, it is an antique Rolex, produced in 1972, the movement is the use of the twentieth century, the sixties to the eighties manual winding machine Core cal.727.