BAD
/VendorService

Payer to payer API

API overview


Utah Medicaid's Payer to Payer API is an enterprise API that implements the HL7 FHIR standard and provides the ability for Utah Medicaid to exchange member data bi-directional with other payers upon member's consent. Member’s consent will be given through our MyBenefits portal through the Opt-in process. This electronic exchange of a patient's health data will happen between their current and previous, or concurrent health insurance plans. The Payer to Payer API implements the FHIR clinical resources as defined by the HL7 FHIR standards.

Payer to Payer Data Exchange will allow the patients to take their information with them as they move from payer to payer over time to help create a cumulative health record with their current payer. Having a patient’s health information in one place will facilitate informed decision-making, efficient care, and ultimately can lead to better health outcomes.

The Payer to Payer API follows the SMART Backend Services security model.

Capability statement


Developers, for the capability statement please reference https://fp.medicaid.utah.gov/PayerToPayer/fhir/metadata , opens in a new tab.
 
The capability statement outlines versions, authorizations, resources, profiles, interactions, search parameters, and end points.

Getting started


In order to access the API, application owners will need to register their PHR application by completing the form found on the PHR App Registration page.

Authorize URL format:

https://sso.mylogin.utah.gov:443/am/oauth2/authorize?client_id={your_client_id}&redirect_uri={your_redirect_url}&response_type=code

Getting access token:

HTTP method: POST

URL: https://sso.mylogin.utah.gov:443/am/oauth2/access_token

 

HTTP headers:

Header name Value
content-type application/json
accept application/json
authorization Basic base 64({client_id}:{client_secret})
 

HTTP body:

Field name Value
code {oauth code}
grant_type authorization_code
redirect_url {your_redirect_uri}

Explore API


API documentation:

https://fp.medicaid.utah.gov/VendorService/developerapi?resource=developer_patient_api , opens in a new tab

Resources


The API supports the following resources:
Resource URL
Coverage

https://fp.medicaid.utah.gov/ProviderClient/Coverage

Endpoint

https://fp.medicaid.utah.gov/ProviderClient/Endpoint

ExplanationOfBenefit

https://fp.medicaid.utah.gov/ProviderClient/ExplanationOfBenefit

HealthcareService

https://fp.medicaid.utah.gov/ProviderClient/HealthcareService

InsurancePlan

https://fp.medicaid.utah.gov/ProviderClient/InsurancePlan

Location

https://fp.medicaid.utah.gov/ProviderClient/Location

Metadata

https://fp.medicaid.utah.gov/ProviderClient/metadata

OperationDefinition

https://fp.medicaid.utah.gov/ProviderClient/OperationDefinition

Organization

https://fp.medicaid.utah.gov/ProviderClient/Organization

OrganizationAffiliation

https://fp.medicaid.utah.gov/ProviderClient/OrganizationAffiliation

Patient

https://fp.medicaid.utah.gov/ProviderClient/Patient

Practitioner

https://fp.medicaid.utah.gov/ProviderClient/Practitioner

PractitionerRole

https://fp.medicaid.utah.gov/ProviderClient/PractitionerRole

RelatedPerson

https://fp.medicaid.utah.gov/ProviderClient/RelatedPerson

StructureDefinition

https://fp.medicaid.utah.gov/ProviderClient/StructureDefinition

Request header:


All API resource requests require the following headers:
Header name Value
content-type application/json
accept application/json
authorization Bearer {ACCESS_TOKEN}

Regulatory information