Stream: DME Orders on FHIR
Topic: stream events
Notification Bot (Apr 29 2020 at 14:59):
Stream created by Nandini Ganguly.
David Bruinsma (May 13 2020 at 20:21):
Welcome all participants. I am here for anyone who has questions. My expertise is in DME management. I am the owner of Colonial Medical Supplies for over 20 years, and with that I have a good understanding of DME order workflows, requirements, documentation, etc. Although I am not a programmer I do have some history with software, programming and fhir. If I am not able to answer your question, I will help to find the expert that can.
Zane Schott (May 14 2020 at 13:37):
Good day all. We look forward to connecting and sending PAO bundles between participants.
Please list 'public' endpoints available for consuming PAO bundles here in this chat session.
Zane Schott (May 14 2020 at 13:52):
Validate PAO Bundles / Resources ...
https://trifolia-fhir.lantanagroup.com/lantana_hapi_r4/post-acute-orders4/import
Chung Ko (May 14 2020 at 14:40):
I have tested my bundle it seems working fine...:-)
Zane Schott (May 14 2020 at 14:45):
@Chung Ko Johnny - Care to share your bundle via Zoom?
Ricardo Quintano (May 14 2020 at 15:09):
My current questions
1. PAOTask - What is the difference of "basedOn" and "focus" elements? It is not clear to me. I am referencing both to DeviceRequest.
2. PAODeviceRequest: How the Sender knows which types of devices are available in the receiver? Should it query from a Catalog from the Receiver?
3. PAODeviceRequest: How the Sender knows the Patient ID that the Receiver will understand? What happens if the patient does exist in the Receiver?
4. PAOSubscription: can you give me an example of a criteria? I don't know how to reference to the task sent in the Bundle.
Danielle Friend (May 14 2020 at 17:16):
Writing up some of what we chatted about on the track earlier today - thanks for the good discussion.
What is the expected capabilities of the service supplier?
Answer: the supplier could have a range of capabilities:
- A sophisticated supplier would likely be able to receive different inbound notifications or messages and query back systematically for supporting information (ex: patient height/weight or latest vital sign readings)
- A small/medium sized vendor may only be able to receive the order message and respond with accept or deny. And ask via annotation for more information. As opposed to being able to query back for data. They often times will rely on an intermediary
Feedback for the spec:
- Call out the different expected capabilities and assumptions in the IG.
- Design the workflow such that it can be expanded to support the sophisticated approach.
- Start with the MVP (minimal viable product)
- @Vassil Peytchev listed some suggested assumptions and workflow updates in FHIR-27101
Additional discussion:
- Coverage and guarantor information is one of the main missing API pieces. Needed to determine appropriate rule based criteria (often zip code and medicare based). Large suppliers and intermediaries often use other integration options to get this information, including non-standards based APIs.
Danielle Friend (May 14 2020 at 17:19):
@Zane Schott and others please add more details if I missed anything from our discussion earlier
Zane Schott (May 15 2020 at 13:06):
Good day all! I am working to add a refresh to the Rotech token for each call and complete the Patient resource injection within the JSON bundle; then do the same with Epic.
Chung Ko (May 15 2020 at 13:11):
Morning Zane! Do you have chance to demonstrate using the query order API with http POST method? The API have the Task.status and Task.StatusREason updated. See if your side can received these from our end point. Thanks.
Johnny
Chung Ko (May 15 2020 at 17:09):
Zane, regarding to the test APIs, it will not be available after the Connectathon as the firewall will be reconfigured to block any traffics from outsider. Please note.
Last updated: Apr 12 2022 at 19:14 UTC
