POST contribution with FLAT composition on EHRBase

Implementation Platform
,
1

I am trying to POST a contribution with a composition in FLAT format using the EHRBase API. It seems there are two possibilities:

  1. “Native”: Directly using the contribution endpoint with the data in FLAT format (seems to not be supported?)
  2. Using the composition endpoint, providing the commital metadata in headers “openEHR-VERSION” and “openEHR-AUDIT_DETAILS” ( see openEHR-VERSION-and-openEHR-AUDIT_DETAILS). According to the EHRBase docs, these headers are implemented, but I have not managed to to store the committal metadata I defined (“openEHR-AUDIT_DETAILS.committer”, “openEHR-VERSION.lifecycle_state”, “openEHR-AUDIT_DETAILS.description” etc.) in the contributions that are created from the request.

I have managed to do both options using Better (1. through openEHR API, 2. through EHR API)

The documentation on EHRBase is quite brief, so I am not certain that I have done it correctly. Are either of these options actually implemented? And more generally, are there any security/authentication details to be aware of when providing committal metadata in the headers of a POST composition request compared to the “native” contribution endpoint?

2

This was discussed at SEC yesterday and there is now CR to document how to support FLAT formats and Contribution metadata in the API .

2 Likes
3

Also, to your second point, it seems we don’t currently support those headers in EHRbase, could you report an issue please in GitHub https://github.com/ehrbase/ehrbase. Thank you

1 Like
4

Thanks for the response, I have reported the issue now,

1 Like