There is quite a bit of interest in the UK in adapting the US-based SMART platform www.smartplatforms.org for UK use. One aspect of SMART involves the definition of a fairly simple API which serves RDF graphs of archetype like objects e.g Blood pressure, allergy. The SMART guys are aware of openEHR and have been quite support of it in the CIMI work, and I understand that they do not see the clinical content definitions underpinning the APIs as core business.
It seems to me that there is an interesting possibility of using openEHR archetypes (probably templated) to define the clinical content which is to be expressed as RDF graphs. This will give a much more adaptable and extensible approach + better model governance etc. It seems to me that the key requirement is to be able to create a run-time artefact, in the same way that we create Template data schema but to output RDF rather than XSD. Is this correct and if so, does anyone have any experience with this? The other interesting aspect is that because the SMART API returns mostly ENTRY-level components, these need to be wrapped in some COMPOSITION level metadata. Does it make sense that we actually return very lean EHR Extracts? Ian -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org
