Please can some one short explain what the difference is between assumedValue and defaultValue in CPrimitive?
Thanks
Bert
Assumed value.
assumed value is a value you set in the archetype. If no value (at all) occurs in the data for that item (e.g. patient position for BP measurement) but applications want a value, they can check the archetype (in fact it will be in the template) to see if there is an assumed value. If there is, it can be used.
I don't believe it has had much use in archetyping over the years.
Default value.
the system or app should pre-populate the field with the default value. If no user value is supplied, it will remain the default. In this case, there is a value in the data.
- thomas
Hi Bert,
Assumed value: This is a statement in an archetype which asserts what should happen if a value is missing. It can really only apply safely to an element is Observation/State or in a Cluster archetype intended for use in state. Essentially this is a design-time statement of ‘clinical knowledge’ and should not end up in data. Personally I don’t use this very often as it can be difficult to know when/how that knowledge can be safely applied. One reasonable example is in OBSERVATION.body_weight.v1 where the ‘State of Clothing’ has an assumed value of ‘Lightly Dressed’.
Default value: Generally applied at template level as it will often differ depending on the exact use-case. A default value does appear in run-time data.
As Thomas,says in his reply, Assumed value has rarely been used but it can sometimes be helpful.
Thanks Ian and Thomas,
Perfectly clear!
Bert
Ian McNicoll wrote:
Assumed value: This is a statement in an archetype which asserts what should happen if a value is missing. It can really only apply safely to an element is Observation/State or in a Cluster archetype intended for use in state.
Ian, it's not only CLUSTER archetypes that can appear within the state of an OBSERVATION archetype:
* An ELEMENT archetype can similarly be slotted into the OBSERVATION.state.
* We should also allow it in EVENT.state. (That's the "Person State" check box that you see in the Archetype Editor when working on an OBSERVATION.)
* The Person State can be defined by an embedded archetype of type ITEM_SINGLE, ITEM_LIST, ITEM_TREE or ITEM_TABLE.
So if the idea is that assumed value should be used only to describe state, then I think that the complete list of places where it would be needed is in:
* OBSERVATION.state
* EVENT.state
* CLUSTER archetypes
* ELEMENT archetypes
* ITEM_SINGLE archetypes
* ITEM_LIST archetypes
* ITEM_TREE archetypes
* ITEM_TABLE archetypes
Peter
Hi All
The reason we introduced the assumed value in the Observation.State was to deal with the fact that many variables may be introduced in regard to the state of the person when an observation is made – clothing, fasting, post-challenge, at rest, on exertion, asleep, upright/sitting/lying etc.
Actually these ‘state’ variables are not recorded but are largely assumed to be of a certain value. So we do not need to say that an ECG is at rest – but we do need to say that it was an exercise ECG. The state variable for exertion is assumed to be at rest unless stated. A blood pressure which is stand alone is assumed to be sitting in most instances. The archetype allows formal expression of what the relevant state variables are and what they are assumed to be when they are missing. This is helpful for standardisation of observations without massive data collection constraints.
Cheers, Sam