Tutorials
Use Cases
Interface
Resources
- AllergyIntolerance
- AuditEvent
- Basic
- Binary
- CarePlan
- CareTeam
- Claim
- Condition
- Coverage
- Device
- DiagnosticReport
- DocumentReference
- Encounter
- ExplanationOfBenefit
- Goal
- Group
- Immunization
- List
- Location
- Measure
- MeasureReport
- MedicationAdministration
- MedicationDispense
- MedicationRequest
- Observation
- OperationDefinition
- Organization
- Patient
- Person
- Practitioner
- Procedure
- Provenance
- Questionnaire
- RelatedPerson
- RiskAssessment
- ServiceRequest
- Specimen
- Subscription
- Task
- ValueSet
Operations
- add
- care-gaps
- classify
- code-terms
- compose-coding-system
- compose-demographic-identifier-system
- compose-identifier-system
- emergency-department
- everything
- get-page
- group-bulk-export
- inpatient
- office-visits
- patient-bulk-export
- remove
- remove-wrong-code-terms
- submit-data
- text-search
- validate
- validate-coding-system
- validate-identifier-system
- visits
Examples & Testing
Endpoints
Provenance helps to track the source and authenticity of other resources.
Overview
See the FHIR documentation for more information about Provenance resources.
Mapped Concepts in HIEBus
Supported Interactions
Provenance resources support the following interactions.
Search Parameters
When searching for Provenance resources, the following search parameters are supported.
| Name | Type | Prefixes
Modifiers |
Can be Chained? | Description |
|---|---|---|---|---|
| _id | Token | :missing | Resource id. | |
| target | Reference | :missing | yes | Target reference(s). |
Sortable Parameters
When searching Provenance resources, it is possible to sort the returned values by the following search parameters.
Only one sort parameter may be specified.
Supported Includes
When searching Provenance resources, it is possible to include the resources referenced by the following field names.
- Target
Have questions about the HIEBus FHIR interface? Contact us at fhir@careevolution.com.
© 2023 CareEvolution, LLC
