FHIR resource link

http://hl7.org/fhir/servicerequest.html

http://hl7.org/fhir/2022Sep/servicerequest.html

FHIR definition
(edited for PSI)

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)

• counseling

• surgeries or procedures

• specialist consultation and assessments

• other clinical interventions.

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

FHIR required properties

status, intent, subject.

PSI required properties*

Header: country & psiProjectCode *

identifier - Voucher code

For active and completed status - see below.

Extensions

Implemented: none

Under consideration:

• none

Sample payload

(minimum set)

PSI tags

Country ISO-3 code

/wiki/spaces/DHM/pages/13992045

PENDING: implementation of this property

Identifier

Voucher code: 12XYZ + control digit = 6 characters.

status

• draft: available ID

• on-hold: taken by an offline application

• active: voucher issued

• completed: voucher redeemed

• revoked: voucher cancelled

• entered-in-error | unknown - not specific use

see voucher page for further info on how this status are assigned at PSI

intent

• proposal: default value for vouchers issued by an social worker/ Chat Bot

• plan: request issued by a health professional - example, HIV confirmatory test?

Other values, probably not applicable to PSI typical use cases: http://hl7.org/fhir/valueset-request-intent.html

subject

Refers to the patient (client) resource id that the voucher was assigned to - Must be completed for status:

• active (issued)

• completed (completed)

authoredOn

For status: active, completed

dateTime that the voucher was issued to the client (patient)

requester

For status:

• on-hold (who took the voucher offline)

• active, completed

Who issued the voucher:

• Practitioner (meaning the health worker)

• If a Bot use XXXXXX

reason

For status: active, completed

dateTime that the voucher was issued to the client (patient)

occurrenceDate

For status: active, completed

when the voucher is expected to be used/ expiration date

note

For status: active, completed

Services/ goods that the voucher can be used for.

patientInstruction

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:

• Multiple times?

• For more than one service?