Hey everyone! I'm Aman, Founder & CEO of Farmako ...
# general
b
Hey everyone! I'm Aman, Founder & CEO of Farmako from the YC S20 batch. We started with an EMR app for the doctors in India; we have a few hundred active doctors using EMR and now provide the simplest way for diagnostic labs to connect with patients on WhatsApp to share reports and book lab tests! We have more than 1M health records on Farmako stored as PDF in S3. We also have some testing data of these reports in structured format as key-value pairs of pathology parameters. We want to convert this data to FHIR! Can someone walk me through the steps?
r
Thanks Aman!
So if I understand correctly, your keys are some kind of code, and your values are the test Value?
b
Yes, it's like {Potassium: "5.3", Sodium: "12"}
r
So there are a few resources you will need to create: 1. A
Patient
resource for the patient details (https://www.hl7.org/fhir/patient.html) 2. An
Observation
resource for each (key,value) pair to record a single measurement (http://hl7.org/fhir/observation.html) 3. A
DiagnosticReport
resource to group the
Observations
into reports (https://www.hl7.org/fhir/diagnosticreport.html)
The
Patient
resource should be relatively self-explanatory, but let me know if you need help. For each
Observation
resource, there are 3 key properties you'll have to set: 1.
status
- either"final" is probably good enough for now 2.
code
- this is where you indicate the type of test that was run, preferably using a standard coding system like "LOINC". (see our docs on Codeable concepts for more info: https://docs.medplum.com/fhir-basics#codeable-concepts-standarding-data) 3. The
valueQuantity
field, which encodes the value and units of the test
b
Thanks for sharing, Rahul! Let me read the docs and do some research and then try it out!
r
For each
DiagnosticReport
resource, the key fields you'll need are. 1.
status
: just set to "final" for now 2. the
code
field: Can just be some text Codeable Concept describing the report type 3. The
result
field, which is an array of `Reference`s to the your Observations
No problem @bhands - the FHIR docs can be a bit hard to parse so I'm happy to answer more questions
Have you been able to register for a Medplum project?
Also, if you're using Typescript, you can take advantage of our Typescript SDK to make reading/writing to the Medplum API much easier (https://docs.medplum.com/sdk)
@bhands I'm also happy to get on a call next week to talk through your use case in a bit more detail
b
That'd be great Rahul! Would love to get on a call and discuss
r
Great - I
b
Let me try it out today first and if doesn't work, would be great to get on a call
r
Sg. you can send me a calendar invite at rahul@medplum.com
b
I worked with FHIR and DICOMs in 2016 when I was trying to make DICOM viewer.
Sure
r
Oh man, so you're an OG
178 Views