Fast Healthcare Interoperability Resources (FHIR, pronounced "fire") is a draft standard describing data formats and elements (known as "resources") and an application programming interface (API) for exchanging electronic health records
We have received quite a lot of interest in using SQL on FHIR data. As you know, FHIR data is encoded in the form of a complex directed graph, and thus you can not easily query it with traditional SQL queries or business intelligence tools. Some customers have noticed that the "FHIR search tables" in IRIS for Health have flattened part of the FHIR graph, and have tried to use them for analytics. This is an undocumented and unsupported part of IRIS for Health, and can change without notice.
https://www.youtube.com/embed/DyBCmLEBJW0 [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
Did you know that with InterSystems IRIS for Health™, you can create a FHIR Facade that enables healthcare apps to send and receive HL7® FHIR® data? Find out how in this learning path(3h 30m), which includes a hands-on exercise(20m).
I have been successfully able to transform hand-written medical test results documents to HL7 ORU_R01 v2.x, then to SDA, which will be trasformed to FHIR or C-CDA.
However, I have a category of documents which contains reference range in multiple date formats, which are measured for each gestation period. For example, below is one of the documents.
FHIR has revolutionized the healthcare industry by providing a standardized data model for building healthcare applications and promoting data exchange between different healthcare systems. As the FHIR standard is based on modern API-driven approaches, making it more accessible to mobile and web developers. However, interacting with FHIR APIs can still be challenging especially when it comes to querying data using natural language.
In our previous article we saw how to configure our EMPI to receive FHIR messages. To do this we installed the FHIR Adapter that InterSystems made available to us that configured a REST endpoint to which we could send our FHIR message. We would then get the message and transform it to a %String that we would send via TCP to the output of our EMPI configured in our HSPIDATA namespace.
Alright, it's time to see how we retrieve the message, transform it back to a %DynamicObject and parse it to the class used by the EMPI to store the information.
Hi all! Wanted to share a recent video we created with InterSystems FHIR expert, Russ Leftwich, covering some of the most frequently asked questions with FHIR. Let us know if you have more questions for a future iteration of this!
https://www.youtube.com/embed/tH2sWhVa8MU [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
In previous articles we have seen how to configure and customize our EMPI, we have seen how we can include new patients in our system through HL7 messaging, but of course, not everything is HL7 v.2 in this life! How could we configure our EMPI instance to work with FHIR messaging?
As said in the previous article about the iris-fhir-generative-ai experiment, the project logs all events for analysis. Here we are going to discuss two types of analysis covered by analytics embedded in the project:
In a fast-paced clinical environment, where quick decision-making is crucial, the lack of streamlined document storage and access systems poses several obstacles. While storage solutions for documents exist (e.g, FHIR), accessing and effectively searching for specific patient data within those documents meaningfully can be a significant challenge.
Watch this video to learn about InterSystems TrakCare Innovation Toolkit which is a free download that enables TrakCare users to quickly access their data in standard HL7® FHIR® format, making the system of record a system of transformation:
https://www.youtube.com/embed/hIGE5GdJaTE [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
Getting the following error when activating a foundation namespace(FHIR Server). Anyone had this issue before:
<THROW>zAddRecordToLogPersistence+7^HS.HC.Util.Installer.1 *%Exception.StatusException ERROR #5001: Attempt made to use $$$ActivationLog* macros before HSSYS exists
I am looking for a way to serialize fhir content received via interoperability adapter into it´s corresponding ISC model class (e.g. HS.FHIR.DTL.vR4.Model.Resource.DiagnosticReport) for later use. In my opinion the outline to accomplish this would be something like
1) Receive the FHIR data 2) Get quick stream containing the JSON data 3) Examine if bundle or single ressource 4) For resource serialize to coressponding model class (HS.FHIR.DTL.vR4.Model.Resource.*) 5) further use of newly created object of type HS.FHIR.DTL.vR4.Model.Resource.*
https://www.youtube.com/embed/aE743TEBgmw [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
Large language models are stirring up some phenomena in recent months. So inevitably I was playing ChatGPT too over last weekend, to probe whether it would be a complimentary to some BERT based "traditional" AI chatbots I was knocking up, or rather would it simply sweep them away.
Watch this video to learn about InterSystems FHIR Server, the turnkey FHIR data solution that empowers FHIR application developers to focus on building life-changing healthcare applications:
https://www.youtube.com/embed/O3Er84CGcoc [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
As you may know, the next release FHIR R5 is currently published in "beta". Right now, it is undergoing a quality review. And we'd like to invite YOU to participate in this process!
Your task, if you wish to accept it 😉, is to check text descriptions, copy editing, and grammar. To facilitate this quality review, ClinFHIR is being used, which is a web tool used for developer education on FHIR and to help developers to visualize FHIR data and to plan out the building of FHIR applications. For instructions on how to do the quality review of FHIR R5 read this short document. The application you will use to do the quality review is here.
This is how ClinFHIR looks in action for this FHIR R5 Quality Review:
Hi All! Wanted to share this new video we've published, which might be of interest to people in the healthcare space. Achieving True Interoperability in Healthcare Systems is all about going beyond the typical "syntactic" interoperability and understanding what's needed to bring that interoperability to the next level in healthcare.
By update
.png)
Open Exchange app
.png)
.png)
.png)
