Add text to EHR spec(s) to strongly recommend UUID as EHR id. Currently it is a HIER_OBJECT_ID, which cannot be changed at this stage, but in fact all implementations use Guids/UUIDs. We should add text to make this the strongly preferred option.
Add text to EHR spec to strongly recommend COMPOSITION.uid be populated (it is optional in the formal model).
For COMPOSITION.uid the type can be HIER_OBJECT_ID (we should also recommend uuid here) or OBJECT_VERSION_ID (this one will be used by the REST API, but the RM admits both as those are UID_BASED_ID inherited from LOCATABLE.uid: UID_BASED_ID).
Do other implementers have ideas on this?
What about "Add test to EHR spec to strongly recommend COMPOSITION.uid be populated (it is optional in the formal model)."? - if I remember correctly the discussions were around whether or not is allowed to have COMPOSITION.uid empty or different than the related VERSION.uid.
I have added that now.