/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document)
...
Document type | Метод REST API |
---|---|
Document title | [DRAFT] [NEW] Mark in error Composition [API-007-011-001-0475] |
Guideline ID | GUI-0011 |
Author | @ |
Document version | 1 |
Document status | DRAFT |
Date of creation | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) |
Method API ID | API-007-011-001-0475 |
Microservices (namespace) | ME |
Component | CompositionCompositions_ME |
Component ID | COM-007-011 |
Link на API-специфікацію | |
Resource | {{host}}//api.ehealth.gov.ua/api/patients/id/encounter_package |
Scope | |
Protocol type | REST |
Request type | |
Sync/Async | |
Public/Private |
...
Check that value is in allowed values from
COMPOSITION_CANCELLATION_REASONS
dictionary.in case of error - return 422 ('value is not allowed in enum')
1.2 Validate value in the field $.status_reason corresponds to the config
Get config parameter COMPOSITION_MARK_IN_ERROR_STATUS_REASON, where Configuration.type=Composition.type and Configuration.category=Composition.catergory
Check that value is in allowed values from COMPOSITION_MARK_IN_ERROR_STATUS_REASON
in case of error - return 422 ('Invalid status reason for such composition type and category')
2. Status
The target status value must be submitted in the order of display in the signed content (media storage)
...