Beda Software

Last week at Sydney technical work group meeting I had a fascinating conversation about Composition, Bundles and DocumentReferences. Andy Bond mentioned that people may start using these resources for a data exchange instead of direct FHIR API calls. Then during the menti session this result were revealed. It seems that a majority of audience exactly want it. Furthermore, you can just use DocumentRefrence for PDF or RTF files. So, does Australian community just want to pack PDF into FHIR and use it as clinical notes correspondence exchange? There are many other ways how you can use Composition, Bundles and DocumentReferences. My preferred one is clinical evidence. Once you finish an encounter you can create a discharge summary as a Composition and then generate a Bundle that contains all referred resources. Then you put this bundle in the immutable file storage. Now it is an evidence artefact that could be used if we have to trace back in time to the moment of the Encounter. Document reference is just a reference to this immutable file. If you need to exchange or update data, you can do it via direct FHIR API calls. You can easily modify the data in the system and keep it up to date. You can resolve conditions modify any historical data on the FHIR server if needed. Because there is an immutable copy of the past data you always can retrieve from a file storage. I would like to have more discussion about such advance use cases in #HL7AU #FHIR #SPARKED community. Let's leave CCDA document-based approach in the past and move to the future of FHIR-native systems Kate Ebrill Heath Frankel Landon Reilly John Grimes Michael Lawley Michael Strachan

I am excited to share how multiple ai tools works together to implement search functionality on top of FHIR API. Everybody is welcome to join.

For the past three years Australian Health IT community achieved a lot. #HL7AU #Sparked connectathons attract not just local vendors anymore. We have international participants. There were two things that I personally want to highlight: - AU Patient summary is a huge topic. I presented FHIR Questionnaire for creating a curated version of AU Patient Summary. It loads patient data into Questionnaire, than a user can modify it and save as Composition. - Health Samurai | Aidbox FHIR® Platform saved e-requesting track. It was the only fully functional AU E Requesting server that was used for exchange. All features we presented during the connectathon is available here https://lnkd.in/gT-xJ-aA So you can try it anytime. There is no need to wait for the next event.

Last week I participated at in-person work group meetings at Hobart. It was a first time for me in Tasmania. Beside reconnecting with all colleagues from #SPARKED and Australian Digital Health community, I got a few important insights about Encounter record. From a data-model perspective, an Encounter Record is more than a single Encounter #FHIR resource. It must encompass related resources such as Observations and Procedures. A compositional approach needed to bundle these elements. So, the Encounter Record could be represented as a subset of IPS or AU PS. I am experimenting with this approach and going to present some outcomes next week on the #HL7 #AU #connectathon in Sydney.

It was my pleasure to show how three systems form different vendors: Health Samurai | Aidbox FHIR® Platform #ontoserver from CSIRO and #BedaEMR from Beda Software work together to create International Patient Summary, share it and display analytics dashboard about immunization data derived from #ips You can try it on your own at https://fhirlab.net If you like to have a YouTube video with this content please leave a comment to this post and I will create it for you.