Dear all, The 'next frontier' will be the various types of "workflow" and the interaction with the EHR and other components in an EHR-system.
Before rushing into quick decisions and quick fixes I call for a study of: - CEN/tc251 System of Concepts for Contuity of Care, ContSys. - CEN/tc251 Health Information Services Architecture, HISA. The first contains the set of concepts dealing with co-operation between healthcare providers around the care of a patient. Several concepts dealing with care plans, clinical path ways in various sorts are defined. The second can help us think about the various levels where types of workflow take place because it defines in a generic way EHR-system components,their inter faces and behaviour. Each type of workflow will use its own model and behaviour of its components. The whole exercise needs to start with a validated set of requirements and the study of some important literature. It is my expectation that En13606/openEHR, ContSys and HISA contain more than enough ingredients to find a good solution. With regards, Gerard -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252 544896 M: +31 653 108732 > >> there are two levels of expression of clinical knowledge, guidelines, >> evidence etc that we can use, namely >> a1) guidelines etc that are mentioned in an archetype, and inform the >> design of the archetype. This can be done as I described. In this >> case, >> the guideline or other knowledge reference is the same for all data >> built from the archetype. >> a2) resources that are referenced on a per-archetype basis, but >> not in >> the archetype, rather they are referenced from the archetype >> classification ontology that indexes archetypes >> b) guidelines referenced in data, i.e. on a per instance basis. On >> the >> model you see here: >> http://www.openehr.org/uml/release-1.0/Browsable/ >> _9_0_76d0249_1109249648736_872559_12384Report.html >> the class CARE_ENTRY has the attributes "protocol" (how / why did I >> create this clinical statement/observation/whatever), "guideline_id" >> that enables the referencing of guideline that caused this Entry >> to be >> created (e.g. maybe some guideline told the doc to measure the BP and >> also ask questions about smoking); ENTRY.workflow_id may also be >> relevant, for Entries created due to workflow execution. >> >> I would think these go close to supporting today's requirements in >> this >> area, although I realise we cannot predict the requirements of the >> future... > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060915/af9a270a/attachment.html>
