Stream: implementers
Topic: Referral Request Specialty
Grahame Grieve (May 29 2019 at 22:48):
We are close to having a complete structure of a Bundle and ServiceRequest which we will be sending to a FHIR API as a means to send clinical referrals. One of the final challenges we still need to solve is ensuring that the receiver can route the referral to the correct department within the Organisation. Ideally this would be based on a HeathcareService speciality which would be selected by the referral requester. This speciality could be one of many available within the HealthcareService and would be provided by a seperate API endpoint available from the client.
In the deprecated ReferralRequest there is a speciality CodeableConcept that we could have used in conjunction with the recipient which would have been the Organisation. However, specialty is no longer an attribute in the ServiceRequest resource. One possible solution is to declare a HealthcareService as the performer of the ServiceRequest with a single speciality listed in the resource itself. This doesn’t quite feel right but we can’t see an alternative. We’re hoping someone can assist or provide guidance.
Grahame Grieve (May 29 2019 at 22:48):
from http://community.fhir.org/t/referralrequest-speciality/1360
Grahame Grieve (May 29 2019 at 22:49):
@Eric Haas ?
Eric Haas (May 30 2019 at 16:47):
Tim Berezny (May 30 2019 at 17:22):
I certainly don't think that having a separate service for each specialty is a bad idea, if in fact your department can receive referrals targeted to various specialties then your department has multiple services.
performerType certainly also seems like a viable approach, you just have some extra complexity though as it relates to your HealthcareService directory, as you now have to pick TWO things instead of one (the Healthcare service + the service's specialty).
Last updated: Apr 12 2022 at 19:14 UTC
