Author Archives: Mark Kramer

One of the most significant claims made by FHIR is out-of-the-box interoperability (see the one page glossy summary on FHIR). This is only true for a weak definition of interoperability. Any well-formed FHIR resource can be parsed by any compliant FHIR application, but this doesn’t mean the … Continue reading →

In the last post, I took up Grahame’s request for feedback on possible alternative syntax for extensions. To review, the goal would be to eliminate the use of the tag and use readable names, similar to the way core elements are represented. It may or may not be possible to improve on the current representation, but it is worth investigating. In the last post, I listed the following requirements… Continue reading →

Recently, Grahame posted a request on his blog requesting feedback on how FHIR represents extensions (http://www.healthintersections.com.au/?p=2467). Currently, all extensions appear under <extension> tags. This makes the wire format hard to read, particularly when there are nested extensions. The worst-case scenario … Continue reading →

Welcome to the LightMyFHIR blog. For several years, folks at MITRE Corporation have been working with and working on FHIR. We have many experiences to share with the broader FHIR community. This blog is one of the ways the MITRE team will be … Continue reading →