Surescripts Record Locator and Exchange Implementation Guide

About Record Locator and Exchange

Surescripts RLE allows requesting locations to electronically discover potential locations of patient records within their source hospital or vendor systems and provides support to retrieve those records using the HL7® FHIR® standard transactions. The Surescripts implementation of RLE provides requesting locations access to the following sources of information:

  1. Surescripts produces an on-demand document known as the Surescripts Location Summary. It is formatted following the Health Level 7 (HL7) standard of a Clinical Document Architecture (CDA). This document may be retrieved using standard FHIR® transactions sent to RLE. Using network transactions to identify healthcare locations where patients have previously received care, RLE will provide the requesting healthcare provider with a CDA containing the names and contact information of the providers/locations where the patient has been seen. This information may then be used to contact those locations to obtain the patient’s records.
  2. When queried, RLE returns informationr equired to retrieve patient documents from other RLE enabled vendor systems. Records may be requested through RLE. Exchange will be facilitated by RLE using record locator transactions to query and retrieve clinical documents from discovered responding locations on behalf of the requesting location.

Responding locations will provide access to patient rosters by sending one of the following: (1) an Admit, Discharge, and Transfer (ADT) data feed or, (2) means to accept FHIR® Patient Search requests from Surescripts.

Responding locations will receive requests for records from Surescripts on behalf of an RLE enabled requester. RLE standard transactions will be sent by Surescripts to query and retrieve patient clinical documents from the responding location.

About this Guide

This Guide was created to assist vendors in developing and transferring messages needed to electronically query locations of patient records from the Surescripts RLE and identify patient records within their source healthcare facilities or vendor systems and facilitate the exchange of records found.

The audience for this document includes any customer responsible for developing a system interface for these RLE HL7® FHIR® messages.

This Guide is meant to support, integrate and further clarify the HL7® FHIR® Specification and best practices as used when transacting through the Surescripts network. It does not reproduce the base standards in their entirety. When developing, this guide should be used along with additional documentation referenced and applicable customary coding standards.

Examples Disclaimer

Examples provided throughout this Guide are not intended to be all-inclusive. This pertains to example workflows, element-specific (field) examples, or message examples. Customers should not restrict coding to the examples used herein.

When developing, this Guide should be used along with the accompanying schema file, additional documentation referenced, and applicable customary JSON or XML coding standards.

Guide Disclaimer

In the event that Customer chooses to make any changes to Customer’s software recommended in this guide, Customer acknowledges and agrees that (1) Surescripts shall bear no responsibility or liability for Customer’s changes or any effects thereof and (2) Customer shall be required to transition to the new guide at such time as said guide is published, which may involve different or additional parameters than are published in this guide.

Reference Material

Surescripts Provided Materials
Connectivity and Authentication Implementation Guide
Record Locator & Exchange ADT EA Draft Supplement
External materials to be obtained by the customer
Carequality Query-Based Document Exchange Implementation Guide
HL7® FHIR® release 3 Standard for Trial Use (STU)