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
Working on implementation FHIR to my project, I found interesting project HAPI-FHIR, which could help me to quickly launch my FHIR api server with InterSystems Caché as a storage, because this projects uses Hibernate to connect to database, as an example they use DerbyDB. I tried to change settings to use InterSystems Caché, but unfortunately it does not work and throw some errors inside HIbernate. As I found in Caché documentation, I have not some many options, I just have to set Cache dialect, and set database url.
I use rest service on Health Connect and will has utilized HL7 FHIR for get information of external database. But i don't find exemplo in oficial documentation. Someone to utilize the HL7 FHIR for info request in to external database?
Having a recent project to create a FHIR repository, I want to know (as looking at the code) if HealthShare FHIR implementaton supports subscriptions?. I know it records the subscriptions ok, BUT does it handle sending the subscription out (based on the tags) to an endpoint (i.e. when a new FHIR request commits data that would trigger the subscription) ?, I'm 50% it doesn't, but would rather find out for sure before shoe horning something in.
1. I saw there are built in DTLs “FHIR.FromSDA” and “FHIR.ToSDA” to convert SDA -> FHIR and FHIR -> SDA. Similarly Do Intersystems have DTLs for HL7 -> FHIR and FHIR -> HL7?
2. The reason why I am asking is, I see in HSLIB namespace HS->GateWay->HL7->HL7toSDA3 and HS->GateWay->SDA3->SDA3toHL7 DTLs. Like-wise I am trying to locate HL7 -> FHIR and FHIR -> HL7. Please help me to locate them
Cures Act USCDI/ C-CDAv21 certification. I am looking for SDA3 examples for Newman-Bates-Kid/registry settings/advices on how to learn / whatever is helpful. InterSystems xsl files are clean but I am not working very often with xsl. I am mainly looking at Provenance and Clinical Notes, the 2 last errors we have. InterSystems documentation, so far I know, is very poor: only classes and some pages. Support has a small knowledge about SDA3 -> C-CDAv21 even if they try very hard to help.
I am new to this forum. So please let me know if this is not the place to post these questions.
I have heard from some previous Intersystems presentations that FHIR profile validation before posting to FHIR server (using $validate) would be available in IRIS for Health. How do I confirm if this functionality is available and if so, on which version of IRIS?
I reached out to Gary Monger yesterday and asked him how he configured Apache for his SMART on FHIR demo? See https://learning.intersystems.com/mod/page/view.php?id=2948. Gary's response was for me to post my question on the Developer Community forum - so that other people can benefit from the answer.
This is what I asked Gary:
I'm after turning a local Health Share instance on my laptop into a SMART on FHIR server.
I am trying to get FHIR Resource using OAuth 2.0 . I get access_token sucessfully but when I use this token i get this type of error in postman. It is showing 401 Unauthorized please suggest any solution.
I need to add some extensions to the HS.FHIR.vSTU3,Model.Resource.Patient class and then use those extensions to convert incoming FHIR JSON to the FHIR Patient Resource and Likewise add functionality to create A FHIR Patient (target class) from my patient database into the FHIR Patient Resource Object (target class)
many months ago I found a tutorial that explained all of this but can no longer find that tutorial.
We have a situation where we want to save the patient photo (or any other attachment) received via FHIR to a persistent property without decoding it. When it is sent out again using FHIR is is stored in the encoded format and need not be encoded. We do not need to decode it for our application. We always use it on another system that retrieves it or saves it via FHIR and therefore it is always received or sent embedded in JSON.