Interweave-ReferralRequest

Notes: Becomes ServiceRequest in R4

FHIR Field

RIO Mapping

Notes

Conformance

Cardinality

referralRequestMethod

N/A - Not mandatory, and not easily available in RIO, so don’t populate in FHIR

The method used to communicate the referral such as fax, NHS e-Referral Service, secure email, etc... HL7 UK FHIR Reference Server

Must Support

0..1

sourceOfReferral

Suggest don’t attempt to map, just use Referral Source Text in RIO as the valueCodeableConcept.text

Value set includes codes based on the following rules:

·       Include codes from http://snomed.info/sct where concept = < 309013001 |Referred by person (finding)

·       Include codes from http://snomed.info/sct where concept = < 306098008 |Self-referral (procedure)

Must  Support

0..1

identifier

Assume would be the same as the resource ID, so don’t use

Must  Support

0..*

status

Map from Status in RIO

Most likely values will be:

active | completed | cancelled

Mandatory

1..1

intent

Fixed to ‘order’

The request represents a request/demand and authorization for action

Mandatory

1..1

type

Default to SNOMED CT 390866009 - Referral to mental health team

Preferred Binding = Valueset-referral-type - FHIR v3.0.2 (hl7.org)

Suggest default to 390866009 - Referral to mental health team

Mandatory

1..1

serviceRequested

Service in RIO

Preferred Binding = Interweave UkCore Care Setting Type

If not possible to map to SNOMED coded, could use local code/display and text

e.g. with system = https://fhir.nottshc.nhs.uk/STU3/codesystem/Rio-ReferralType

Must  Support

0..*

priority

Referral Urgency in RIO

Possible mapping:

1 = stat

2=urgent

3=routine

http://hl7.org/fhir/STU3/valueset-request-priority.html

routine | urgent | asap | stat

Could map from

Must  Support

0..*

subject

Patient referred to care or transfer

Mandatory

1..1

authoredOn

Could use Referral Created Date or Referral Received Date/Time in RIO

When the service was requested

Note – only one date in the data standard, so will need to choose which date to use from RIO

Probably best not to map to Referral Accepted Date, as that is an Optional field

Must Support

0..1

requester.agent

Referrer in RIO

Could just use requester.agent.display if RIO field is free text

Must Support

0..1

recipient

Team Referred To in Rio

HCP Referred To in Rio

ReferralRequest supports multiple recipients of different types

Note – could create Organisations/Practioners for all possible teams, or use a contained resource

Mandatory

1..*

reasonCode

Referral Reason in Rio

Suggest use local codes/descriptions

Must Support

0..*

note, or

description

Could map Referral Comments to note.text or description if these are used extensively and it is felt they would add value to the consumer

Comments made about referral request

optional

0..*

Supporting.Info

Associated Documents

Reference to a DocumentReference Resources

Note: probably a nice to have … but an option to consider linking to Associated Document

optional

0..*