I was reviewing the REST and common-change control specs, and found there is missing information about how to do an attestation through the REST API.
For instance, a POST to …/composition needs some extra headers so the server can construct the ORIGINAL_VERSION, CONTRIBUTION and its AUDIT_DETAILS
openEHR-VERSION.lifecycle_state: code_string="532"
openEHR-AUDIT_DETAILS.change_type: code_string="251"
openEHR-AUDIT_DETAILS.description: value="An updated composition contribution description"
openEHR-AUDIT_DETAILS.committer: name="John Doe", external_ref.id="BC8132EA-8F4A-11E7-BB31-BE2E44B06B34", external_ref.namespace="demographic", external_ref.type="PERSON"
For the attestation via POST …/composition I was looking for something like:
openEHR-ATTESTATION.proof="..."
openEHR-ATTESTATION.reason="..."
I think that is missing from the spec, and also some comment on how those headers should be used to construct the corresponding attestation instance.
Note that is only for the POST …/composition and maybe for PUT …/composition too, because on the POST …/contribution we can actually send attestations in the payload, though we don’t have attestations in the request examples.
What do others think? sec?