C-CDA was created because they do not know openEHR? :)

-- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150120/738be8a0/attachment.html

C-CDA was created because they do not know openEHR? :)

There is some work going on t odo mappings between openEHR and C-CDA as part of the EU SemanticHealthNet project but I suspect C-CDA has little future, to be rapidly replaced by FHIR, I think this recent tweet is relevant - The #argonaut project, CCDA on #FHIR at #HL7WGM

CRUD Restlet

Hi Thomas, The interesting question is: what style of service should be used for e-health business entities, like active care plans, managed medication lists, and order management, which all need much more complex APIs than just 'get'? FHIR is not designed for this kind of thing, and it's

C-CDA was created because they do not know openEHR? :)

://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150120/3deba37b/attachment.html

openEHR-technical Digest, Vol 35, Issue 33

-- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/atta chments/20150120/738be8a0/attachment-0001.html -- Message: 2 Date: Tue, 20 Jan 2015 07:54:25

openEHR-technical Digest, Vol 35, Issue 33

HI William, I know for a fact that archetype-based CDAs do/did exist, because Ocean built them for Nehta (not many though, it's not that easy to do it). However, Nehta is notoriously sensitive with IP, and may well have refused them to be made public. I have also seen some other technical

openEHR-technical Digest, Vol 35, Issue 33

-- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/atta chments/20150120/738be8a0/attachment-0001.html -- Message: 2 Date: Tue, 20 Jan 2015 07:54:25 + From: Ian

openEHR-technical Digest, Vol 35, Issue 33

attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150120/cca21d89/attachment.html

CRUD Restlet

I too have looked how the approach used by FHIR could be applied generically to openEHR, but at the entry level using TDDs. I actually went up one level and considered the principals of the HL7-OMG RLUS specification, which is the logical basis of FHIR before they hard coded the resources. RLUS

CRUD Restlet

://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150120/38f42ffa/attachment-0001.html

CRUD Restlet

-- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150120/14e410aa/attachment.html