Open industry specifications, models and software for e-health
Forums | Wiki | Blogs | Jira | CKM | Accounts

Blogs


- Woland's cat - Archetypical - Musings of a confused technology addict. - Blog - Atomica Informatics -


Bridging the interop chasms | Blog - Atomica Informatics

27-11-2015

True or false: if we want to achieve any degree of semantic interoperability in our clinical systems we need to standardise the clinical content, keeping it open and independent of any single implementation or messaging formalism?


Why US will have better clinical decision support than the EU | Musings of a confused technology addict.

18-11-2015

For many, smarter healthcare through the use of computers is an exciting idea. This has been the case since the sixties, and I belong to the current generation of people who try to make this happen. There are so many misunderstood things about making computers help clinicians. It would take a lot of space to …


Incoherence ain't all bad! | Blog - Atomica Informatics

12-10-2015

Incoherence is not ideal, but it is a realistic part of any work such as we are doing within the openEHR community. Transparency and openness can mitigate some of the incoherence. Within a transparent, governed and collaborative environment incoherence and apparent conflict can be recognised and leveraged constructively to improve the quality of archetypes.


A little dance, clap & cheer | Blog - Atomica Informatics

14-08-2015

"For the first time in Australia, we have strong evidence of the benefits of eHealth records in bridging the gaps in information that occur as patients move between different healthcare providers in the public and private sectors."


Case Study: Clinical Engagement | Blog - Atomica Informatics

13-08-2015

Bridging the gap between the clinical experts and software engineers involved in eHealth projects is well known for being difficult and frustrating for both sides. The openEHR methodology is having great success in bringing the non-technical clinicians along with us on the clinical modelling journey.


Brazilian EHR innovation, powered by openEHR | Blog - Atomica Informatics

11-08-2015

Watch what is evolving in Brazil... It is largely a greenfields nation as far as electronic health records is concerned, which gives it a great opportunity to make bold and innovative decisions, avoiding many of the pitfalls of those who have gone before and the constraints of legacy systems.


Fractal exam findings II | Blog - Atomica Informatics

09-08-2015

The scope and diversity of clinical content in the physical examination domain is huge and complex, with different clinicians requiring different levels of detail. We have developed a base pattern for recording physical examination findings, knowing that the concept-specific detail within each model will need be added as backwardly compatible revisions of these archetypes. In this way they will evolve in an organic way to suit clinical requirements, but within a tightly governed environment.


Fractal exam findings I | Blog - Atomica Informatics

09-08-2015

The extremely complex nature of the clinician's physical examination is an obvious benchmark test for the capability of any modelling paradigm. If you can't model the clinical requirement for something as fundamental, yet frustratingly diverse as physical examination, then you need to go back to the drawing board until it works. This post outlines our journey...


Archetype patterns | Blog - Atomica Informatics

18-07-2015

Through trial and error and implementation and iteration, we are starting to identify pragmatic and sensible patterns that will fast track future archetype development, but there is no denying that it has been a long and slow process to get to this point…


The challenge for FHIR: meeting real world clinician requirements | Blog - Atomica Informatics

12-11-2014

With the increasing burden of technical engagement resulting from the incredible expectations generated by FHIR globally, perhaps the clinical content specification should be outsourced to... the clinicians first of all, ensuring that the clinical content can be represented in a technical format for implementation.



Acknowledgements: Atlassian (Jira, Confluence) | NoMagic (MagicDraw UML)
AsciiDoctor (publishing) | GitHub (DVCS) | LAMP dev community