FHIR Chat · Redox Conversion

When the wifi works, we have two endpoints to explore. Post plain-text HL7 to either of these endpoints, and you will receive a FHIR messaging bundle in either STU3 or STU4 format (or an error message as to what went wrong).
http://redoxfhir.ngrok.io/v4
http://redoxfhir.ngrok.io/v3
Currently we support ADT, SIU, and ORU messages - will be working throughout the weekend as we discuss additional mappings / corrections.
@Brendan Keeler and @Benjamin Flessner are available (currently at table 20).

Benjamin Flessner (May 04 2019 at 14:01):

Noticed a couple of messages come through already with errors - while we should handle \r, \n, or \r\n as line delimiters, the message didn't have anything; so make sure to put line breaks between segments (when copying from the confluence examples, at least, I had to manually re-add the line breaks.

Kumar Satyam (May 04 2019 at 14:55):

Posted a V2 ADT message with AL1 segments. I received a bundle without allergy information. Bundle doesn't have all the mappings for patient.

Brendan Keeler (May 04 2019 at 14:59):

Correct. We don't process allergy as it is. What else is missing?

Brendan Keeler (May 04 2019 at 16:17):

By the way, your message with allergies has the allergy code as the allergy reaction

Brendan Keeler (May 04 2019 at 16:18):

AL1-5 is for the reaction (so not seafood)

Benjamin Flessner (May 04 2019 at 17:45):

@Kumar Satyam We don't do mother's maiden name yet, and I noticed we were missing a phone number from your example (which has now been re-added if you want to try again).

I've added some allergy mappings now in ADT messages. Like Brendan said - the allergen name would need to be in AL1-3.2, not in AL1.5 which is reaction. But give it a shot with some allergy-containing ADT messages.

Marcelo caldas (May 04 2019 at 18:38):

When the wifi works, we have two endpoints to explore. Post plain-text HL7 to either of these endpoints, and you will receive a FHIR messaging bundle in either STU3 or STU4 format (or an error message as to what went wrong).
http://redoxfhir.ngrok.io/v4
http://redoxfhir.ngrok.io/v3
Currently we support ADT, SIU, and ORU messages - will be working throughout the weekend as we discuss additional mappings / corrections.
Brendan Keeler and Benjamin Flessner are available (currently at table 20).

Are those links live? i tried but it's redirecting to 0.0.0.0:9000?

Benjamin Flessner (May 04 2019 at 18:45):

Yes; they're just API endpoints to POST to; they won't resolve to serve up a webpage.

Brendan Keeler (May 04 2019 at 18:47):

Hey Marcelo!
Those are URLs you can POST to from cURL, Postman, or another tool. We're over at the HL7v2 to the FHIR table if you need help.

David Hay (May 05 2019 at 10:16):

@Benjamin Flessner - do you plan on leaving those endpoints live post-connectathon?

David Hay (May 05 2019 at 10:20):

I have something similar (a POST endpoint) that utilizise a node-red engine in the background. No where near as complete as yours though...

I also have a simple UI that drives the process (select a v2 message, let you see it, send the message to the engine, validate and display the result) that should work with your API as well. Might be interesting to expose this for others to use, again post-connectathon...

David Hay (May 05 2019 at 10:28):

BTW the API is not running right now - right?

David Hay (May 05 2019 at 10:42):

@Keith Boone - this API could be the standard transform operation you were talking about - and the message source could be the github repo where you are putting the sample messages...

Benjamin Flessner (May 05 2019 at 13:20):

For now it's just running locally on my laptop; I shut it down last night since no one hit it after 4pm, but I can certainly leave it up throughout the week. Longer team we're certainly looking into setting up something like this permanently on our public engine. It's the same code we use in production today, but it's used for translating communications from source health systems to destination applications. For the connectathon, I've short-circuited the code to return the FHIR bundle rather than sending it onto a different destination. If this is useful, or you have additional suggestions or questions, please let me know!