...
ACTOR is abstract, so we’ll need concrete types
Sync SM specs
Add
/registry/person/{version_uid}
and/registry/versioned_person/{versioned_object_uid}
Add
/registry/agent/{version_uid}
and/registry/versioned_agent/{versioned_object_uid}
Add
/registry/group/{version_uid}
and/registry/versioned_group/{versioned_object_uid}
Add
/registry/organisation/{version_uid}
and/registry/versioned_organisation/{versioned_object_uid}
Add
/registry/role/{version_uid}
and/registry/versioned_role/{versioned_object_uid}
Add
/registry/party_relationship/{uid}
Add also
/registry/contribution/{contribution_uid}
similar to/ehr/{ehr_id}/contribution/{contribution_uid}
Initially we discussed about /registry
endpoint but we'll keep this for later (a new RM Entity?) and in the meanwhile we'll use /demographic
as that matches current Demographic IM component name.
see also Pablo’s proposal
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
TAGs
see 2023-06-05/07 Barcelona SEC Meeting tags suggestion (todo Sebastian Iancu )
...