Facilitating patient data exchange with compliant solutions and flexible technology. (Image)

“Facilitating patient data exchange with compliant solutions and scalable technology.”

Purpose-built. Simple. Powerful.

AMR Web Services is a software interface which affords easy integration and patient data exchange for HIEs, Hospitals and our Channel Partners (EHRs/EMRs/Practice Management software vendors), through a simple but powerful API.

With Access My Records, partners can focus on the development and evolution of their primary service or product offerings. Integrated partners rely upon AMR to deliver the leading patient portal technology needed to complement those offerings; often reducing or eliminating their in-house development costs.

Additionally, AMR provides the patient-facing support; which eases operational burdens often associated with extended consumer care and service. Our purpose-built, easy-to-use, easy-to-integrate solutions provide our partners a complete, leading-edge solution for modular integration or standalone use.

Multi-device access by integrating the AMR Patient Portal or PHR (Image)

A Low-Touch Integration Solution: 'Auto-Create'

AMR provides its partners the unique ability to auto-create a patient portal “presence” within its ONC Certified patient portal, upon first receiving a CCD or CDA via Direct Messaging. AMR’s Direct Messaging is enabled within the healthcare community’s trusted HISP-based network through its HISP-to-HISP partnership with Surescripts™.

Auto-Create is a unidirectional Direct data-feed 'pushed' to AMR. Examples of use include: a provider that may be using a function-limited EHR/EMR/PM; or a Health Information Exchange (HIE). In either such scenario, the low-touch auto-create ability affords our partners an interoperable and cost-effective solution to provide the patient a secure AMR Patient Portal™ account.

HL7 XML Data Handling of CCD, CDA, and Hybrid records. (Image)

Auto-Create Breaks the Data Silo.

Prior to the Auto-Create option, patient-data exchanges could only be tightly integrated with the provider's EHR/EMR software in order to be effective. That data restriction perpetuated legacy and data-silo barriers; effectively binding patient data to some proprietary software provider—forcing those records to stay within network boundaries.

Connecting Doctor and Patient via the HIE.

An additional benefit of Auto-Create is the added capability of provider-to-patient secure communications via the Provider Portal using Secure messaging. (Such as: General communications, Appointments, Prescription refills and Provider referrals.)

This is a unique feature that allows for HIEs to offer secure messaging to the patient and provider using Auto-Create. Effectively, HIEs cause the introduction of both parties to AMR and then AMR connects the two parties technologically at the patient and provider portals. After the HIE introduces the patient and the provider, the patient and the provider can then communicate using Secure Messaging via AMR’s web facing patient and provider portals independent of the HIE. The HIE is still involved and will independently continue to feed patient data from the provider to AMR.

Standards-based Integration Formats (Image)


AMR Portal Web Services APIs are built on an ASP.NET base using SOAP. The APIs use standard web services protocols that transfer messages in XML format and are typically sent over HTTP giving developers access to the required functions and methods for integration with AMR Patient Portal™. AMR Portal Web Service uses SSL (Security Socket Layer) over HTTPS to securely communicate and encrypt the data exchange and communications between AMR Patient Portal™ and the EHR vendors’ software.

The AMR Patient Portal™ uses a CCD data structure as part of HL7 and we support CCDs as a vehicle for sharing actual document files between patients and providers and between providers. Our API will also support CCDs as part of the interface. There are a number of APIs used to “sync up” for both patients and providers and there are a number of APIs that pass specific patient data. We use the CCD construct as a payload on the APIs where patient (clinical, visit, lab, comprehensive) data is passed between us and the EHR/EMR.