IHE PCC Referral Status Query
0.0.1-current - ci-build International flag

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

2:3.Y6 Retrieve Referral Status [PCC-Y6]

This section corresponds to transaction [PCC-Y6] of the IHE Technical Framework. Transaction [PCC-Y6] is used by the Referral Status Query Client and Referral Status Query Server Actors. The Retrieve SDOH Referral Status [PCC-Y6] transaction is used to query and get back results.

Scope

The Client [PCC-Y6] transaction passes a go Request from a Client to a Server.

Actors Roles

Table: Actor Roles

Actor Role
Referral Status Consumer Sends query to Provider
Referral Status Provider Receives the query and responds

Referenced Standards

FHIR-R4 HL7 FHIR Release 4.0

Interactions

ConsumerProvider1. SDOH Referral Status Query [PCC-Y6]2. SDOH Referral Status Query Response [PCC-Y6]

Figure X.X.X.X-1: SDOH Referral Status Query Interactions


SDOH Referral Status Query

This interaction uses the FHIR Search mechanism to obtain the current status of an existing referral, based on the referral identifier.

Trigger Events

The Consumer system or user is authorized to query for the status of an existing SDOH referral, and based on user action or a business rule within the system, it sends are query to the Referral Status Provider.

Query Semantics

The query is a FHIR search against either a Task or ServiceRequest resource. The formal list of parameters is describer the SDOH Referral Status Consumer CapabilityStatement definition.

Expected Actions

'’TODO: define expected actions’’

Go Response Message

Trigger Events

'’TODO: define the triggers’’

Message Semantics

'’TODO: define the message – usually with a StructureDefintion’’

Expected Actions

'’TODO: define expected actions’’

CapabilityStatement Resource

Server implementing this transaction shall provide a CapabilityStatement Resource as described in ITI TF-2x: Appendix Z.3 indicating the transaction has been implemented.

  • Requirements CapabilityStatement for Client
  • Requirements CapabilityStatement for Server

Security Considerations

See MHD Security Considerations

Security Audit Considerations

'’TODO: The security audit criteria ‘’

Client Audit

'’TODO: the specifics’’

Server Audit

'’TODO: the specifics’’