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 a mixture of legacy and new systems, and are grappling with the issue of moving documents between systems.
At the moment we are mostly using file drops and encoding metadata in filenames, but a new supplier (letter transcription) is going to provide a Hl7v2 feed sending MDM^T02 messages with PDF's of letters base64 encoded in the message itself.
We are thinking of asking all our suppliers to go with MDM (or ORU) for sending documents.
I'm interested in the pros and cons of the options; and if there are options I haven't thought of.
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.
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.