On 16/12/2015 10:54, Bert Verhees wrote:
On 16-12-15 11:37, Diego Boscá wrote:
but there is an example of an specialized identifier in that same
document
e.g.
"uk.nhs.clinical::openEHR-EHR-SECTION.t_encounter_report-vital_signs_headings-0001.v1"
in
http://www.openehr.org/releases/AM/latest/docs/AOM2/AOM2.html#_an_example
Thanks Diego, for pointing this out, I checked it in RM 1.0.3
ArchetypeId, and there is indeed a specialization-numbering in the
archetype identifier.
So this information will become redundant in the archetype, available
in the concept/root-node id, and in the archetype id.
This is not good, according to many programming standards which advise
to not have redundant information.
Because it adds nothing, and if it differs, it is not trustworthy.
that's why it is gone in ADL2/AOM2.
The new ARCHETYPE_HRID class is the one that matters, and it does not
know about specialisation depth.
- thomas
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
