Skip to Navigation | Skip to Content

openEHR-Technical mailing list archives

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Should ATTESTATION.reason datatype really be DV_TEXT or rather DV_CODED

  • To: For openEHR technical discussions <openehr-technical@openehr.org>
  • Subject: Should ATTESTATION.reason datatype really be DV_TEXT or rather DV_CODED_TEXT (or perhaps CODE_PHRASE)?
  • From: Erik Sundvall <erik.sundvall@liu.se>
  • Date: Fri, 26 Feb 2010 15:11:53 +0100

Hi!

Here comes yet another possibly stupid question...

Do we ever want the attribute ATTESTATION.reason to be a DV_TEXT
instead of a DV_CODED_TEXT?
Is this a possible improvement for the specification (common IM rev
2.1.1 from release 1.0.2) or is there an intention behind being that
liberal?

The spec says the value for  ATTESTATION.reason should come from the
terminology group "attestation reason".

A less important sidetrack:

Is the use of the more verbose DV_CODED_TEXT instead of just
CODE_PHRASE for fields/methods like VERSION.lifecycle_state and
AUDIT_DETAILS.change_type there for human readability reasons or what
is the purpose? Are end users really supposed to see the DV_TEXT.value
of those? I guess aplication logic and GUIs are better off trying to
use the embedded CODE_PHRASE than relying on the possibly language
dependent DV_TEXT.value for those fields/methods.

Best regards,
Erik Sundvall
erik.sundvall@liu.se http://www.imt.liu.se/~erisu/  Tel: +46-13-286733
_______________________________________________
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical