Separating Models from Implementation

[borut.jures]

@ToStupidForOpenEHR

Directors come back to me and say, we really like the idea, and would like to adopt the clinical models developed by OpenEHR, but our architects have looked at OpenEHR and the specification programme and decided it’s not something we can invest the time and effort in. It’s too much of a heavy lift.

Did the directors propose an alternative for the CDR?

I don’t see how the CDR part could be simplified. They will spend more time and effort if they start building it from scratch (they might prefer this as it is more profitable for those building it).

The ISV applications that connect to the CDR are already simplified with WebTemplates, Simplified Data Templates. If that is too complicated for the ISVs then they shouldn’t work on the projects that are outside their competencies.

Would a generated ORM model help the ISVs? Or even as a higher level library to the CDR data?

---

Not meant as a self promotion but I want to show you that there are many options how to approach what you describe:

@borut.jures

I can read my first OPT2 JSON

…and I have to write only a single line of code to do it:

…everything else is generated from the BMM files.

When I started working with openEHR I hoped this could be done. 40 days later I know it can be done. All thanks to the computable specifications.

It would be a valuable information to understand what the directors expect. If you can help us understand their expectations/requirements then we may start working on providing what they wish for.

I’ll be happy to spend some time generating a proof-of-concepts.