ServiceRequest - FHIR
- Rodolfo Melia
- Carlos
- James Chang
|
|
|---|---|
FHIR resource link | |
FHIR definition | ServiceRequest represents a proposal or plan or order for a service to be performed that would result in a Procedure or DiagnosticReport This resource may be used to share relevant information required to support a referral or a transfer of care request from one practitioner or organisation to another. Examples include: (list edited for PSI)
The ServiceRequest resource allows requesting only a single procedure. If a workflow requires requesting multiple procedures simultaneously, this is done using multiple instances of this resource. |
PSI use case | Use for managing vouchers |
Required properties | see below |
Extensions | Implemented: none Under consideration:
|
Sample payload (minimum set) | {
"resourceType": "ServiceRequest",
"id": "144235",
"meta": {
"versionId": "2",
"lastUpdated": "2023-07-12T08:12:48.645+00:00",
"source": "#pOsuiFSdYdvNq6of",
"profile": [ "SRH_HIV-SWZ" ]
},
"identifier": [
{
"system": "http://sample.info/voucher-seq-no",
"value": "208078"
}
],
"status": "completed",
"intent": "proposal",
"code": {
"coding": [
{
"system": "http://sample.info/voucher-code",
"code": "059XWB"
}
]
},
"occurrenceDateTime": "2023-07-06T10:27:38.883Z",
"requester": { "reference": "Practitioner/554" },
"subject": { "reference": "Patient/140895" }
} |
Notes for ServiceRequest FHIR resource, per property
Property | Required by PSI? | Notes |
|---|---|---|
PSI tags | Yes [psi] | PENDING: implementation of this property |
Identifier | Yes [psi] | Voucher code: 12XYZ + control digit = 6 characters. |
status | Yes [fhir] |
see voucher page for further info on how this status are assigned at PSI |
intent | Yes [fhir] |
Other values, probably not applicable to PSI typical use cases: http://hl7.org/fhir/valueset-request-intent.html |
subject | Yes [fhir] | Refers to the patient (client) resource id that the voucher was assigned to - Must be completed for status:
|
authoredOn | optional [psi] For status: active, completed | dateTime that the voucher was issued to the client (patient) |
requester | optional [psi] For status:
| Who issued the voucher:
|
reason | optional [psi] For status: active, completed | dateTime that the voucher was issued to the client (patient) |
occurrenceDate | optional [psi] For status: active | when the voucher is expected to be used |
LocationReference | optional [psi] For status: active | Location the voucher is expected to be used |
note | optional [psi] For status: active, completed | Services/ goods that the voucher can be used for. |
patientInstruction | optional [psi] For status: active, completed | Details of the message with the voucher share with the client (method of sending, date and time of sending) |
??? Redeem date | Extension??? | AN array? Or better to have links from the services and goods back to this voucher ? What happens if this voucher can be used:
|