Stream: implementers
Topic: Converting Raw Data into FHIR format Prescription
jagjot singh Wadali (Jul 14 2021 at 13:32):
Hi Everyone,
I am new to FHIR Format and have certain queries.
In our Application, we have patient's prescription data saved in the different tables in the database. For a single prescription, there are several columns including physical examination & history, allergies, medication, advice, diagnosis, etc for a specific patient.
I need to write a c# code where I can convert all this prescription information including patient information into FHIR format. I had tried writing c# code but I faced some issues:-
We don't have any FHIR server implemented but just have to map the data from the database in FHIR, in this case, certain terminologies I don't understand are taken from the FHIR server. For example
"entry": [
{
"fullUrl": "Composition/3b990853-f0fa-4046-8388-d71dd93a0fa1",
"resource": {
"resourceType": "Composition",
"id": "3b990853-f0fa-4046-8388-d71dd93a0fa1",
"identifier": {
"system": "https://www.max.in/document",
"value": "3b990853-f0fa-4046-8388-d71dd93a0fa1"
},
In the above-mentioned example, I don't have any Composition in the FullURL parameter.
In the prescription format specified in SNOMED CT, this is the code for Prescription 440545006. And in the JSON structure of prescription, there is an only practitioner, patient, and medication however there is no information regarding allergies or diagnosis or complaints. How to include all this information in prescription FHR
I tried to create a model class from JSON, but certain parameters remain null which doesn't make a valid FHIR format.
Anyone who had implemented Converting raw data into prescription in c# kindly help.
Rik Smithies (Jul 14 2021 at 14:01):
Is there a reason you are starting with a Composition? May be better to look at MedicationRequest for a prescription
Lloyd McKenzie (Jul 14 2021 at 15:50):
From a FHIR perspective, it sounds like you're doing more than what we would typically call a "prescription" - you're capturing a full set of information for an encounter. Drug prescriptions in most of the world typically don't link to allergies, physical, etc. You could potentially link some of that information in using MedicationRequest.supportingInformation. Conveying allergies there would make sense if you were justifying the use of a specific "non-preferred" med due to an allergy, but you generally wouldn't convey all allergies, just the one or set that was relevant to that specific order. Similarly, you might convey height, weight, liver function or other observations that are relevant to the order. Providing all details from a examination & history would be unusual. Diagnosis would generally go in MedicationRequest.reason
Brian Beatty (Jul 14 2021 at 18:51):
if your data is sourced from multiple tables, look into creating a view with a union, or using linq's union method
Last updated: Apr 12 2022 at 19:14 UTC
