FHIR specification

See the following -

Composable Software, Collaborative Development, and the CareWeb Framework

The CareWeb Framework (CWF) enables the software developer to build complex, richly interactive, web-based applications in a modular fashion...The CWF has been used as the basis for a complete EHR and CPOE system and has been ported to several open source EHRs, including OpenMRS, VistA, and RPMS. The CWF is open source software built upon open source software. Read More »

Grahame Grieve on What Project Argonaut Means for the HL7/FHIR Community

Project Argonaut was announced last week. You can see the announcement here. That press release was intended for an external community, and didn’t address lots of important questions for the HL7 community itself. So here’s an outline of what project Argonaut means in practice for HL7.

Read More »

Grahame Grieve's FHIR report from Baltimore HL7 Meeting

Last week, HL7 held it’s annual plenary meeting in Baltimore at the Hyatt Regency...For the FHIR project, our main attention was the ballot. Across the core standard, and multiple implementation guides, we received >800 detailed comments as part of the ballot. This represents a slight increase over the last ballot, but there was a clear change in the focus of the comments – there was a significant drop in the number of comments relating to the infrastructure, and much more focus on the domain content, and it’s applicability to real world problems. This is a clear marker of the growing maturity of the standard. We continue to expect that we’ll publish FHIR release 3 at the end of this year.

Test-Driven Development With FHIR

While preparing for, and participating in, the recent FHIR Connectathon 11 held in Orlando, Florida, yet another benefit of FHIR’s implementer-friendly philosophy became apparent to me – the ability to facilitate Test-Driven Development (TDD). TDD has been defined as “a software development process that relies on the repetition of a very short development cycle: first the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards.” Dating back to 2003, TDD is now considered by many developers to represent the state of their art – shining some much-needed light on the darkness might be another way of looking at it!

Read More »