hl7.org/fhir

Kick off a FHIR Bulk Data system-level $export with type filtering and poll for completion

Implement FHIR Bulk Data $import to ingest NDJSON resources into a FHIR server asynchronously

Authenticate a backend service for FHIR Bulk Data access using SMART Backend Services client credentials flow

Handle the 202 Accepted / Content-Location / X-Progress async pattern for long-running FHIR operations

Collect a SDOH screening using Gravity Project Observation profiles and record social risk findings

Create an SDOH Goal aligned with Gravity Project profiles after identifying a social need

Implement a Gravity Project closed-loop SDOH referral using ServiceRequest and Task resources

Query US Core profiles for a patient's clinical data ensuring MustSupport element compliance

Map USCDI v4 data classes to US Core 7.0.0 profiles and verify required data element coverage

Implement FHIR R5 topic-based Subscriptions using the R4 backport IG for new lab result notifications

Invoke the FHIR $everything operation to retrieve a complete longitudinal patient record

Expand a FHIR ValueSet using the $expand operation and validate a code using $validate-code

Record FHIR Provenance resources to document data lineage and chain of custody for clinical resources

Model and submit a FHIR Consent resource to enforce data sharing restrictions on patient data

Execute a FHIR Bulk Data $export at the system level with _typeFilter to export only specific resource types meeting a filter criteria, then download and process the resulting NDJSON files

Implement a FHIR Bulk Data group-level $export to export data for a specific cohort of patients defined by a FHIR Group resource, then reconcile exported data against the group membership

Implement a CDS Hooks service that responds to order-select and order-sign hooks from an EHR to provide real-time clinical decision support cards with suggestions and links

Implement FHIR R4 topic-based Subscriptions (R5 backport) to receive real-time notifications when specific resource changes occur, using a REST-hook channel

Use FHIR terminology services to expand a ValueSet using the $expand operation against LOINC and validate a code using $validate-code against a SNOMED CT value set

Query a FHIR server using _revinclude to fetch Provenance resources that reference returned resources, and interpret provenance to trace the origin and chain of custody of clinical data

Implement FHIR patient matching using the $match operation to find the best matching Patient record in a server when integrating data from an external system

Model and query FHIR Consent resources to enforce data sharing restrictions when responding to FHIR queries, applying patient consent to filter what data is returned

Implement USCDI v4 data class requirements by mapping required data elements to their corresponding US Core profiles and ensuring complete MustSupport field population when writing FHIR resources

Build a FHIR Bulk Data import pipeline to ingest large volumes of FHIR NDJSON resources from an external source into a FHIR server using the proposed $import operation or alternative bulk import patterns

Implement TEFCA QHIN-facilitated exchange by submitting and receiving FHIR queries through a QHIN participant connection for a treatment purpose treatment of care use case

Implement FHIR R4 resource versioning and use the history interaction ([base]/[Resource]/[id]/_history) to retrieve the complete version history of a clinical resource and detect changes between versions

Implement a FHIR-based care coordination workflow using Task resources to assign, track, and complete referral tasks between a referring provider and a specialist, with ServiceRequest linking the clinical order to the task