Inconsistency in REST API Create EHR implementations -needs spec clarification?

I’m strongly against making exceptions or workarounds or relaxing things in rest api specs - let’s keep specs consistent and predictable. So we should keep name and archetype_node_id mandatory, those are not really noise.

If you need some artifacts, here I’ve upload some close to what we use in our production: EHR_STATUS a locatable?

1 Like