How would we do this? There is a method of implementation in problem oriented records whereby a header, generally the ‘problem’, is linked to other record entries or elements that are to do with that problem.
So ‘chest pain’ as a problem may be linked to blood tests, clinical notes, ECG, CXR and medications that were ordered or reported as part of the work up of that condition. In interfaces this allows for views of the record showing the Problem and all linked events/entries/data. It’s essentially what Larry Weed used to talk about. Of course things may relate to more than one Problem, Problems may link to each other, Problem headers and content will change over time. There is usually a fair amount of manual curation, which may be very contextual, but theoretical a lot of it could be automated. By modelling this linkage in data it would become computable, and potentially make some clinicians very happy in their work! Is this something that is part of openEHR specification or that can be modelled in archetypes? Or is it down to the application to manage this? Thanks for any help. As always slightly anxious that am missing something completely obvious, so apologies if so!! Paul Dr Paul Miller GP, Glenburn Medical Practice Clinical Lead, NES Digital Service Mobile/WhatsApp: +44 7711 346 938 -- -- Dr Paul Miller MBCHB MRCGP FFCI DRCOG DMI Glenburn Medical Practice Fairway Avenue Paisley PA2 8DX Tel: 0141 884 7788 http://www.glenburnsurgery.scot.nhs.uk/ Clinical Lead NES Digital Service https://nds.nes.digital/ Mobile: +44 7711 346 928 Twitter: @docpaulmiller
_______________________________________________ openEHR-clinical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
