Hi, in EHRBASE it was decided to add support for CONTRIBUTION or EHR_STATUS and FOLDER.
I’m in charge of designing the conformance tests and test cases to verify such service and found a couple of cases I would like to discuss with the community.
- ‘incomplete’ EHR_STATUS
When committing CONTRIBUTIONs we will have VERSION<EHR_STATUS> inside, and VERSION has lifecycle_state which can be incomplete, complete or deleted.
What would it mean to have an ‘incomplete’ EHR_STATUS? Is that even valid?
- Updating EHR_STATUS and losing data
If we create an EHR providing an EHR_STATUS that has PARTY_SELF.external_ref, that will contain the ID of the patient associated with the EHR.
Then if we commit a CONTRIBUTION with VERSION<EHR_STATUS> and that EHR_STATUS has a NULL external_ref in the PARTY_SELF, or a different ID, the previous PARTY_REF/OBJECT_ID will be overwritten.
Should the update process just create a new version of the EHR_STATUS without the information that was previously there?
What I see is: if we want to update, for instance, is_modifiable on an EHR, we will need to provide the full PARTY_SELF each time to avoid losing patient IDs.
(I know we are not really losing anything because of versioning but when querying we will get just the latest versions).
PS: something we detected is change_type create/delete shouldn’t be supported when committing a CONTRIBUTION with VERSION<EHR_STATUS>.