-
Join 1,155 other subscribers
Subscribe
-
Past Posts
- Why using expressions in workflow is wrong
- A Lingua Franca for e-health takes shape with GraphiteHealth
- The Health IT Platform – a definition
- What is interoperability?
- Directions in clinical guideline programming – CHA2DS2-VASc
- Design-by-Contract (DbC) v Test-Driven Design (TDD)
- Software – from Development to Use and Ownership
Categories
- Computing (43)
- Culture (3)
- decision support (3)
- FHIR (19)
- Health Informatics (92)
- openehr (66)
- Philosophy (7)
- Politics (2)
- standards (48)
- Uncategorized (2)
- workflow (1)
Recent Comments
- David Kerr on Design-by-Contract (DbC) v Test-Driven Design (TDD)
- Athanasios Anastasiou on Why using expressions in workflow is wrong
- wolandscat on Why using expressions in workflow is wrong
- Athanasios Anastasiou on Why using expressions in workflow is wrong
- wolandscat on Towards a standard analysis of computable guidelines, clinical workflow, decision support and … the curly braces problem
General ICT
Health IT
Technology
Tag Archives: API
openEHR REST API 0.9.0 out for comment
The REST API Team (Bostjan Lah, Erik Sundvall, Sebastian Iancu, Heath Frankel, Pablo Pazos, and others on the openEHR SEC and elsewhere) have made a 0.9.0 Release of the openEHR ITS (Implementation Technology Specifications) component, in order to make a pre-1.0.0 release … Continue reading
Making FHIR work for everybody
FHIR is the HL7’s modern approach to connecting components in the health computing space. Unlike the HL7v2 message approach, FHIR is oriented to enabling applications connect to back-ends. It has been running for a few years now, and is doing good work on how to … Continue reading