Presenting IHE on FHIR at FHIR-DevDays

I’m excited to teach two IHE classes on FHIR DevDays in Boston. The FHIR DevDays event focuses on informing IT professionals about the latest health care standards, FHIR – Rapid Interoperability Resources. The Fhir specification is in fact the last in medical care, but is supported by all people who have developed the previous standards (eg HL7, CDA, IHE, XDS, DICOM), while the best experience and the latest RESTful API API. More information on FHIR Dev Days can be found at

Both programs are focused on using IHE for FHIR. The first tutorial focuses on a general view of IHE and Fhir engagement and a comprehensive look at the current 22 IHE files that benefit from Fhir. This is the most interesting tutorial for a general audience interested in standard facilities and development of IHE profiles. This tutorial is a short version of the IHE-on-FHIR education program presented at the HL7 meeting in Cologne.

The second tutorial deepens the use of IH of Fhir to allow access to the infrastructure for replacing API documents based on XDS and / or XCA. Exchanges of these documents are located in the US, Canada, Europe, and other countries. The document exchange environment gives clinicians the ability to publish documents (such as CDA, C-CDA, DICOM, PDF, etc.), such as: B. medical summary, attention cycle, summary of discharges, lab results, X-rays, computed tomography, magnetic resonance, MHD IHD profiles refer to how Fhir allows applications to discover new documents, extract and publish.

The expanded IHE capabilities demonstrate how these documents can be broken down into more natural available FIR resources, the source is linked back to the source document from which the information comes FIR resources.

The appearance of HL7 FHIR is exciting and the collaboration with IHE demonstrates strong support. I always hope to work with the new platform to speed up the progress of medical care.

My articles on FHIR blogs and the exchange of documents and privacy.

Leave a Reply

Your email address will not be published. Required fields are marked *