Well, you can treat ‘referral’ as an order. (FHIR actually treats it like one as ReferralRequest). You can do something like this in Orders tab
- Have a group (maybe do department wise or type) in the orders section. You can type some comments, but not details. Orders table has a column “comment_to_fulfiller” which can be used.
- You can use different queues to list the referral types.
- Then use the ‘order fulfilment’.
The problem is that in Step 1, you will probably want to add more information like the specific provider (orders table does not have any column for that), or a different facility (no provision for that too). And its probably best to define a specific interface.
What I would instead suggest is
- Use Forms 2.0, where you can define additional components too if you want
- Extend the form not just to include observations, but other details. Our Forms 2.0 supports that, but will need additional work to support non obs data. The design is already there, but you need to extend
- GET/POST to another API other than EMR API. The facility is already there to some extent.
- Use the orders table (create a different order type), create a separate table for referral details (provider, facility etc). Note support for location, provider are already there in the forms 2.0, as complex obs, but you will probably have to extend that.
- Use a fulfilment form for referral - that will update the status of the order and other details.