# Questions about the assertion process

**URL:** <https://discourse.openehr.org/t/questions-about-the-assertion-process/11479>\
**Category:** Specifications\
**Tags:** attestation\
**Created:** [5 October 2025 18:14 UTC](https://discourse.openehr.org/t/questions-about-the-assertion-process/11479 "2025-10-05T18:14:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pablo](https://discourse.openehr.org/user_avatar/discourse.openehr.org/pablo/32/3505_2.png) [@pablo](https://discourse.openehr.org/u/pablo)\
**Post date:** [5 October 2025 18:14 UTC](https://discourse.openehr.org/t/questions-about-the-assertion-process/11479/1 "2025-10-05T18:14:09Z")

</div>

I’m checking the assertion model and process, and some questions came up.

For instance:

> Attestations can be added at any time **after** committal of the content being attested.

REF: [Common Information Model](https://specifications.openehr.org/releases/RM/latest/common.html#%5C_attestation_2)

Then a couple of lines below:

> Signing content **at committal** : for some reason, the information being committed needs to be digitally signed.

The first line says assertion should happen after the content is committed, then the second gives the possibility of attestation at commit time. Isn’t that a contradiction?

Another thing, in the REST API it doesn’t seem like we support attestations. For instance on `create composition` we need to use extra `openEHR-AUDIT_DETAILS.xxx` headers [REF2] because we don’t have that that in the payload to generate the audit info in the server for the CONTRIBUTION and ORIGINAL\_VERSION that need to be generated when a COMPO is created. Though we don’t have `openEHR-ATTESTATION.xxx` headers described there, to be able to create the attestation at commit time (note we neither have those headers for the `composition update` where we could attest a COMPO after its initial commit).

REF2: [APIs Overview openEHR specs](https://specifications.openehr.org/releases/ITS-REST/Release-1.0.3/overview.html#tag/Requests_and_responses/HTTP-headers/openEHR-VERSION-and-openEHR-AUDIT_DETAILS)

@thomas.beale @sebastian.iancu what do you think?

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [6 October 2025 11:35 UTC](https://discourse.openehr.org/t/questions-about-the-assertion-process/11479/2 "2025-10-06T11:35:39Z")

</div>

> [@pablo](#):
>
> The first line says assertion should happen after the content is committed, then the second gives the possibility of attestation at commit time. Isn’t that a contradiction?

It doesn’t say an attestation should be added after commit of the original content - just that it can be. Both are valid.

---

<div class="post-metadata">

**Author:** ![pablo](https://discourse.openehr.org/user_avatar/discourse.openehr.org/pablo/32/3505_2.png) [@pablo](https://discourse.openehr.org/u/pablo)\
**Post date:** [6 October 2025 21:46 UTC](https://discourse.openehr.org/t/questions-about-the-assertion-process/11479/3 "2025-10-06T21:46:03Z")

</div>

@thomas.beale Though if you read the first phrase it doesn’t imply that the attestation can be added at the **same** time as the commit, it implies it can **only** add an attestation **after** the commit, though at any time, but after.