Flexpa
Contact usDeveloper Portal

Getting started

  • Introduction
  • Quickstart
  • Use cases
  • Pricing
  • Patient access
  • Test mode
  • Going live
  • What we don't do
  • ChangelogUpdated
  • FAQ

Guides

  • Reading resources
  • Searching resources

Network

  • Payers
  • Endpoints

Tools

  • Flexpa Link
  • Flexpa API
  • Data analytics
  • Connections

FHIR Resources

  • Overview
  • AllergyIntolerance
  • CapabilityStatement
  • CarePlan
  • CareTeam
  • Condition
  • Coverage
  • Device
  • DiagnosticReport
  • DocumentReference
  • Encounter
  • ExplanationOfBenefit
  • Goal
  • Immunization
  • Location
  • Medication
  • MedicationDispense
  • MedicationRequest
  • Observation
  • Organization
  • Patient
  • Practitioner
  • PractitionerRole
  • Procedure
  • Provenance

About

  • Handbook
  • Brand kit
  • Join us
  • Privacy Policy
  • Privacy Notice
  • Security
  • Terms of Service

Provenance

GET https://api.flexpa.com/fhir/Provenance

  • Provenance is a base FHIR Resource ( JSON example)
  • It provides meta information (e.g., action type, date/time, author) for the target resource
  • Commonly available via US Core Provenance Profile

Provenance is a supporting FHIR resource that provides meta information about the target resource. You can think of Provenance as the authorship of a resource, as it is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource.

In contrast to many of the other resources in the Flexpa that are patient-specific, it serves as a supplementary resource that supports the clinical and financial resources in the API by giving versioning of that resource over time. As a result, Provenance is most often used as part of a unique revinclude parameter in a search request or is accessed via a read with a specific FHIR resource ID obtained from a financial or clinical resource. Many payers will not support open searches for this resource.

As a supporting resource, many payers make this available, but many only support a read operation and do not fully support search.

Sample request

While some servers may support a resource-level search without any parameters, very few do for Provenance. We recommend using the format below with a specific resource ID as a search parameter.

This is a sample request using curl to retrieve the Provenance data for a specific AllergyIntolerance resource

ACCESS_TOKEN=flexpa-link-access-token

curl "https://api.flexpa.com/fhir/Provenance?target=AllergyIntolerance/4e329898-43ea-e611-8128-0a69c1b3225b" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Sample response

This is a sample response from Anthem (CareEvolution) using Flexpa API in test mode

Status TwitterGitHub

© 2023 Flexpa. All rights reserved.

On this page
  • Sample request
  • Sample response