Friday, November 15, 2013

Everest Developer’s Handbook 2nd Edition Out

With the release of Everest 1.2 and Everest Framework for Java I’ve had an urge to update the developer’s handbook. To keep it current, as well as ensure that any common questions I get can be fed into it.

Well, the wait is over! Developer’s handbook 2nd edition is out. New in this edition are:

  • Discussion about the Java Edition of the Framework
  • Java samples (where applicable)
  • Updated .NET documentation around some of the new features of Everest
  • Discussion of the mobile components of the Everest Framework

All that adds up to about 60 more pages of content. The new version is available on Lulu as an eBook (http://www.lulu.com/shop/justin-fyfe/advanced-everest-developers-handbook-ebook/ebook/product-21278619.html;jsessionid=91BF5A0F7EF1D9B19919BB7912F441E5) or Hard Cover (http://www.lulu.com/shop/justin-fyfe/advanced-everest-developers-handbook/hardcover/product-21300345.html). As always, proceeds will continue to go toward continued development of the Framework (or at very least some coffee for our development team).

Monday, September 16, 2013

FHIR / PIX Interoperability

Well, its been a while since I’ve written about FHIR, and after lots of interesting exercises in trying figure out “where that goes” I have a working FHIR interface on the Client Registry. I’d thought about sharing some of the interesting use cases I’ve been able to test, and which I hope can be demonstrated at the FHIR CAT this weekend.

FHIR Registration with PIX Registration to XDS Registry

This was the first use case I tested. Basically registering a simple patient record via a POST to http://cr.marc-hi.ca:8080/fhir/0.11/Patient results in an ITI-44 to our XDS registry. This allows an iPad app to create a patient which is then propagated to an affinity domain (i.e. you can have FHIR interface notify another PIX manager)

FHIR Query of an ADT (ITI-8) Registration from an HIS

The second demonstration that I’ve tried is sending an ADT^A01 to the PIX manager and retrieving that data using the FHIR query. I’ve also been able to update the information via FHIR and retrieve the changes via a QBP^Q22 message.

Additionally, the business logic of a client registry (auto/manual-merging, fuzzy matching, auditing, etc.) triggered on the FHIR interface as well.

I’ll post more updates as they are available. Our plan is to take the software to the FHIR CAT and the IHE CAT in January. FHIR may be useful in mobile IHE profiles and this provides a good POC and can identify gaps (it is great to see how a system like this might behave).

Interfaces are available publicly:

FHIR: http://cr.marc-hi.ca:8080/fhir/0.11/
PDQ/PIX Version 2: llp://cr.marc-hi.ca:2100
PIXv3: http://cr.marc-hi.ca:8080/PIXManager
PDQv3: http://cr.marc-hi.ca:8080/PDQSupplier
HL7v3 (CA): http://cr.marc-hi.ca:8080/cr