Hi Silje, You can't turn a string into a DV_TEXT but you can use something like a namespace which is sort of hinted at in the description, which refers to the type being structured
e.g "uk.gov/dvla/driving-licence" I think this is actually a better solution than formal coding as most of these types will be very local/national. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation ian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On Thu, 20 Dec 2018 at 10:40, Bakke, Silje Ljosland < silje.ljosland.ba...@nasjonalikt.no> wrote: > Hi, > > > > In the documentation for the DV_IDENTIFIER data type ( > https://specifications.openehr.org/releases/RM/Release-1.0.3/data_types.html#_dv_identifier_class), > the attribute ‘type’ is described as “Optional identifier type, such as > prescription , or Social Security Number . *One day a controlled > vocabulary might be possible for this.*” (my emphasis). Is it possible to > code this at the moment, given that the data type for ‘type’ is String and > not for example DV_TEXT? > > > > Kind regards, > *Silje Ljosland Bakke* > > > > Information Architect, RN > > Coordinator, National Editorial Board for Archetypes > Nasjonal IKT HF, Norway > > Tel. +47 40203298 > > Web: http://arketyper.no / Twitter: @arketyper_no > <https://twitter.com/arketyper_no> > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
