Hi Pablo,
You news to be clearer about the requirement. Depending on the real
requirement the student may be right.
Remember that demographic model is recording instances of parties not
classes. So if the requirement is to record the specific instance of device
recording attributes such serial
Hi Pablo,
The EHR-CLUSTER archetype were created for some specific use cases,
where it is necessary to record demographic information within the EHR
itself, because the demographic
entity is not supported by the external Demographics service, for
technical or legal reasons e.g 3rd party carers or
I'm correcting student papers for the openEHR course in spanish.A student has
modelled oftalmologic studies for diabetic patients, with a demographic
archetype of AGENT class to model all the devices used on the test.
It could be very usefull to let record the device information in the ACTION
Hi Pablo,
There is a CLUSTER.device archetype -
http://www.openehr.org/knowledge/OKM.html#showarchetype_1013.1.17 - plus a
CLUSTER.device_details archetype -
http://www.openehr.org/knowledge/OKM.html#showarchetype_1013.1.844 - that
might be of interest.
These are modelled as openEHR EHR
Hi Heather!
So the partern to follow is: if you have a demographic concept that should be
part of the clinical record, extract the internal structure to a CLUSTER and
create an slot to that. Is that the global solution?
BTW, there's no device modelled as AGENT on the demographic archetypes,
5 matches
Mail list logo