Premera home Sign in Developers Do you develop digital applications (such as mobile apps)? If not, this information is probably not useful for you. Interoperability developer portals To meet and comply with federal Centers for Medicare and Medicaid Services (CMS) interoperability requirements, we are providing these instructions for app developers. Here you’ll learn how to connect to and consume the Patient Access API and the Provider Directory API. What’s interoperability? It is the way people can control which apps they allow (or deny) access to their personal and private health data. Go to My Health Data Terms of service Compliance and agreement to our Terms and Conditions is required to access and use interoperability APIs. Specific products Patient Access API Provider Directory API Patient access API developer registration Begin the registration process for using the Patient Access API Overview The Patient Access API is required to be protected by the OpenID Connect flow of the OAuth 2.0 specification. This makes it harder for developers to access and test the API as they must present the JWT in the HEADER of the HTTP GET request. Before any development starts, you need several things to help set up the project and begin to access the Patient Access API. A key value and a secret value. These are created when you register an application. URL to initiate the authorization workflow (which includes the user authentication step) A list of return URLs that the identity provider will accept (which one is desired is passed in as part of the URL to start the flow to perform OIDC authorization) Sandbox access Assumption: Developers are familiar with FHIR and the CARIN for Blue Button® implementation guide Sandbox access Sandbox access is provided upon request and allows a developer to get started quickly. It includes a user account with a specific set of data that can be validated against and provides complete functionality. Initial sandbox access includes an application key (unique GUID) and a return URL that can be localhost on any port. Production access Production access is requested after validating that access to the Patient Access API is functioning well. There is no form for this. Access should be requested by responding to the original email sent when you requested sandbox access. A new authorization flow URI and new app GUID will be issued. The return URL for production must also be provided. Once those elements are provided and incorporated into the app, it should be fully capable of querying production data. Provider Directory API developer guide Overview The provider directory is an open access API that doesn’t require a user account. Make sure you’re familiar with the implementation guide for provider directory. In the insurance world providers sign contracts to participate in certain networks. These networks are then assigned to insurance policies that are sold to customers. To find the providers that will accept a given insurance policy requires traversing multiple FHIR elements. The insurance plan to provider relations is as follows: Insurance Plan > Network (represented by FHIR Organization resource) > PractionerRole > Practioner Endpoints Host and base URL Examples Find provider by name Find provider by NPI Find insurance plans a provider accepts Find providers in an insurance plan Need help? Contact PBCinteropdevhelp@project-connect.com Get Connected About Us Pharmacy Guidance Visit Premera Facebook page Visit Premera Twitter page Visit Premera Youtube page Visit Premera LinkedIn page Language support Español中文Tiếng Việt한국어PусскийTagalogУкраїнськаភាសាខ្មែរ日本語አማሪኛOromooالعربيਪੰਜਾਬੀDeutschລາວKreyòl AyisyenFrançaisPolskiPortuguêsItalianoفارسی Premera Blue Cross complies with applicable federal civil rights laws and does not discriminate on the basis of race, color, national origin, age, disability, or sex. © 2021 Premera Blue Cross is an independent licensee of the Blue Cross Blue Shield Association serving businesses and residents of Alaska and Washington State, excluding Clark County.