Do we need an "invalid_artefact" call status type for the I_DEFINITION_ADL2 interface?
Description
There are codes for invalid_archetype and invalid_template. Since I_DEFINITION_ADL2 works with "artefacts", and I_DEFINITION_ADL2.upload_artefact() mentions the output of "invalid_artefact", do we need to add "invalid_artefact" to the DEFINITION_CALL_STATUS_TYPE? Or will use invalid_archetype and invalid_template depending on the resource type uploaded via I_DEFINITION_ADL2.upload_artefact() ?
Environment
None
Activity
Show:
Thomas Beale
February 13, 2019, 2:41 PM
I will add invalid_artefact and document this as the error code for the relevant calls in I_DEFINITION_ADL2.
Pablo Pazos
February 26, 2019, 4:45 AM
Seen the change on the commit, and the generated HTML, and looks good!
REFS:
https://github.com/openEHR/specifications-SM/commit/3da77e559887a52a61bf1f2f4c2e38520c09a608
