signComposition

Purpose

This method is designed to sign an existing composition

Specification

Link	https://app.swaggerhub.com/apis/bugzi11a/emal/1.0.8#/main/signComposition
Resource	/patients/composition/{compositionId}/sign
Scope	composition:sign
Components	Compositions
Using Dictionaries	API paragraph not found
Using Microservices	API paragraph not found
Protocol type	REST
Request type	PATCH
Sync/Async	Async

Logic

Preconditions

API paragraph not found

Global and configuration parameters

None

Input parameters

Input parameter

Values

Type

Description

Example

compositionId

String ($uuid)

(path)

Composition object ID

Filters

None

Request structure

See on SwaggerHub

Request body

Request body with signed Composition. Signed content must match the existing Composition object

Example

Request body example

{
  "data": "string"
}

Authorize

API paragraph not found

Headers

API paragraph not found

Validate request (JSON schema)

API paragraph not found

Validation data request

API paragraph not found

Processing

API paragraph not found

Response structure

See on SwaggerHub

Example:

Response example

{
  "data": {
    "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "status": "PENDING",
    "eta": "string",
    "doneAt": "string",
    "links": [
      {
        "entity": "eHealth/composition",
        "href": "composition/0daaad78-6cfb-11ea-9cd6-afab698838bc",
        "error": "string"
      }
    ]
  }
}

Post-processing processes

None

HTTP status codes

HTTP status code	Message	What caused the error
200	In the case of successful creation of the task of signing the Composition
400	Invalid request format
500	Subordinate service error

Backward compatibility

API paragraph not found