>
> Not sure about mixing URIs with UIDs... OTOH, usually easy to detect by
> parsing.
>
there's a URI format for UIDS: urn:uuid:{lowercase}That's the best to handle mixing them Grahame > - thomas > > On 19/12/2016 09:22, Heath Frankel wrote: > > I think it should be a strong recommendation rather than mandatory > considering it is currently optional and the need for backward > compatibility. > I also think it maybe difficult to apply consistently in some cases such > as feeder data. There are cases in CDA profiles where there are mandatory > IDs and you have to populate it with something but then need to some how > retain this same ID over revisions etc. > I also think a uri should be an allowed type of UID to support ids that > are not guids and possibly associated with real world ids such as lab > result ids, etc. > > Regards > > Heath > > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > -- ----- http://www.healthintersections.com.au / [email protected] / +61 411 867 065
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
