IHE PCC Referral Status Query
0.0.1-current - ci-build
IHE PCC Referral Status Query, published by IHE Patient Care Coordination Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/PCC.SDOH.RSQ/ and changes regularly. See the Directory of published versions
| Official URL: https://profiles.ihe.net/PCC/SDOH-RSQ/CapabilityStatement/IHE.SDOH-RSQ.client | Version: 0.0.1-current | |||
| Active as of 2024-06-14 | Computable Name: IHE_Referral_Status_Consumer | |||
Copyright/Legal: IHE http://www.ihe.net/Governance/#Intellectual_Property |
||||
CapabilityStatement for the Referral Status Consumer Actor in the Patient Care Coordination Technical Framework Supplement PCC SDOH Referral Status Query. See https://profiles.ihe.net/PCC/TF/Volume1/ch-38.html. The IHE Profile text is Normative, this conformance resource is Informative.
The Consumer obtains the status of an existing SDOH Referral by querying the SDOH Referral Status Provider based on the referral identifier.
ServiceRequest or a Task resource.Raw OpenAPI-Swagger Definition file | Download
Generated Narrative: CapabilityStatement IHE.SDOH-RSQ.client
application/fhir+xml, application/fhir+jsonNote to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
clientThe Referral Status Query Client has the capability to query a Server for the status of a previously accepted referral. The query is accomplished via FHIR Search against the ServiceRequest or Task resources. The choice of which resource is used depends on the architecture of the implementation.
Recommend ATNA, encouraged IHE-IUA or SMART-app-launch
search-systeminteraction.The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| ServiceRequest | y | y | _id, identifier | ||||||
| Task | y | y | _id, identifier |
resolvesread, search-type.Using FHIR search on the
ServiceRequestresource as part of transaction [PCC-Y6] allows to find out the status of an existing referral.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | _id | token | Logical id of this artifact |
| SHALL | identifier | token | The business identifier representing the referral identifier |
Using FHIR search on the
Taskresource as part of transaction [PCC-Y6] allows to find out the status of an existing referral.
| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | _id | token | Logical id of this artifact |
| SHALL | identifier | token | The business identifier representing the referral identifier |