Subscribe
-
Past Posts
- Directions in clinical guideline programming – CHA2DS2-VASc
- Design-by-Contract (DbC) v Test-Driven Design (TDD)
- Software – from Development to Use and Ownership
- Nominalism versus Ontology
- Aide Memoire for Computable Domain Models
- Clinical Decision Logic Fun
- Towards a standard analysis of computable guidelines, clinical workflow, decision support and … the curly braces problem
Categories
- Computing (42)
- Culture (3)
- decision support (3)
- FHIR (18)
- Health Informatics (89)
- openehr (63)
- Philosophy (7)
- Politics (2)
- standards (44)
- Uncategorized (2)
Recent Comments
- wolandscat on Directions in clinical guideline programming – CHA2DS2-VASc
- Kevin Coonan, MD on Directions in clinical guideline programming – CHA2DS2-VASc
- wolandscat on Design-by-Contract (DbC) v Test-Driven Design (TDD)
- Michael Miller on Design-by-Contract (DbC) v Test-Driven Design (TDD)
- Andrew Reilly on Design-by-Contract (DbC) v Test-Driven Design (TDD)
General ICT
Health IT
Technology
Tag Archives: persistence
No SQL databases, documents and data – some misunderstandings
A good friend pointed me to this post: why you should never use MongoDB. It’s a very interesting post, about how bad MogoDB turned out to be for dealing with social network data. It’s not that MongoDB is bad per se, just … Continue reading
Posted in Computing, Health Informatics, openehr
Tagged Health Informatics, mongodb, nosql, openEHR, persistence
4 Comments
wolandscat