In the context of exposing a unique Identifier at Entry level e.g for
FHIR mapping, I wondered about concatenating the composiitonUid (inc.
version) with an Entry UID. i.e Versioning (as now) is handled at
composition/contribution level.
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44
On 16/12/2016 02:37, Bjørn Næss wrote:
If you add UID on ENTRY level and you want to use that for some
referencing/look up functionality:
How do you handle versioning of Compositions and its content? Is it a new
entry UID for each version ?
same UID across versions. There is a way to
What kind of identifier should this be? ENTRY is not versioned. Will this UID
be a version independent identifier or should it also keep references across a
version hierarchy?
I agree that there are good reasons to add some identifier on an ENTRY. And it
must not be mandatory - because it
If you add UID on ENTRY level and you want to use that for some
referencing/look up functionality:
How do you handle versioning of Compositions and its content? Is it a new
entry UID for each version ?
Here are description on some functions we have added to DIPS Arena EHR Server
to make it
4 matches
Mail list logo