I’m diving into the world of treatmen/care plan in elderly care and mental healthcare. Especially in elderly care there is a desire to link a goal to a problem. While translating the goal archetype : I noticed an element named ‘clinical indication’ that allows for a DV_TEXT entry. I wonder how does a…

I think that if you need such a tight coupling between ‘goals’ and ‘problems’ you might consider a template in combination with ckm-published or self-made archetypes (if the use case is not covered by the ones already published). This will allow you to specify constraints that makes sense semantical…

Thanks @ian.mcnicoll the link class is what I was looking for I think. I already suspected this would be a complex topic. So reading the spec on the link class I believe I grasp what it does. It can store a link between two (or more) entries and describe the relation. I have a few followup questio…

Interesting suggestion, I will give it some more thought on a more awake moment of a day:) Wondering now how this will simplify the maintanance of the links. Because every problem is stored within the care plan composition?

How does one model that an element could potentially link to another element/archetype entry at design time? So the ‘indication’ element from EVALUATION.goal should only be linkable to an EVALUATION.problem_diagnosis. The main usecase for this constraint would be to be able to present the user wit…

Our current implementation rely on FOLDER to collect entries belonging together. It sees like a nice trade-off for maintaining the connections between data, being able to track who committed which data and for querying. Still this is hard to get right.

Quick related question to the SEC members: Do we have an API endpoint that allows to create links between existing LOCATABLES? How are LINKs being created currently? Best, Pablo.

Hi Pablo, how would you create a link without updating a locatable object, e.g. inside a composition? Or should the endpoint take care of this as an implicit operation?

Hi Birger, by looking at the current model: https://specifications.openehr.org/releases/RM/latest/UML/diagrams/RM-common.archetyped.svg There are two options IMO: Consider LINK a first-class citizen in the model, so it could have it’s own endpoint in the API, thus, that endpoint should handle al…

[image] joostholslag: How does one model that an element could potentially link to another element/archetype entry at design time? So the ‘indication’ element from EVALUATION.goal should only be linkable to an EVALUATION.problem_diagnosis. The main usecase for this constraint would be to be able…

Thanks a lot Sebastian. Based on the advice in this thread, primarily yours and a valuable conversation with @ian.mcnicoll we are leaning towards using FOLDERs to structure and link (semantically and technically) the information in a plan. I would like to link to (my reply) in this related topic fo…

Linking in openEHR: goals and problems

Specifications RM

thomas.beale (Thomas Beale) 5 March 2021 13:29 15

See this new post.

Topic		Replies	Views
Problem-oriented records and querying by problem Technical (archive)	34	188	30 January 2015
Nursing Diagnosis, correct Archetype Ask IEB archetype	14	239	10 February 2026
Can a persistent list be considered the source of truth? Clinical archetype	17	520	28 May 2024
Problem Oriented Medical Record Clinical pomr	21	3560	26 August 2024
Archetype pattern Technical (archive)	20	129	17 February 2018
Linking multiple compositions with a "compound composition" Implementation	14	499	10 April 2025
Medication order - preparation details Ask IEB	19	762	18 December 2021
Care plans in the real world Implementation	6	1140	18 May 2022
Choice between data element and SLOT? Clinical archetype	41	2283	8 March 2021
Philosophy fun - model questionnaires literally or via existing archetypes? Clinical archetype , questionnaire	16	1763	9 September 2020

Linking in openEHR: goals and problems

Related topics