ЕСОЗ - публічна документація
RC_(MC-1189)_[NEW] Generate Composition print form
Overview
This web service allows to generate print form for Composition.
Key Points
ABAC rules are used here:
Employee with active declaration (declaration) - @rule_1
Composition created in the employee's MSP (also author and attester) (recorder_legal_entity_id) - @rule_2
Employee can read all the composition data of episodes created in the employee's MSP (also author) (context_episode_id) - @rule_3
Employee with active approval can read all the data (including merged persons/prepersons data) of specified in approval patient - @rule_4
Employee with active approval can read all the data of specified in approval episodes (context_episode_id) - @rule_5
Specification
Authorization
Verify the validity of access token
in case of error - return 401 (“Invalid access token”) in case of validation fails
Verify that token is not expired
in case of error - return 401 (“Invalid access token”)
Check user and client scopes in order to perform this action (scope = 'composition:read')
return 403 (“Your scope does not allow to access this resource. Missing allowances: composition:read”) in case of invalid scope(s)
Validations
Check Compositions with such id exists in patients collection
in case of error - Return 404 ('Composition is not found')
Validate query parameter
form_type
corresponds to appropriate dictionary COMPOSITION_PRINTFORM_CODESin case of error - Return 404 ('value is not allowed in enum')
Validate that in this method is allowed such
form_type
get config parameter COMPOSITION_PRINTFORM_ALLOW_CODES
in condition array find condition that corresponds query parameter
form_type
in check array must be filled “
MIS
“ - itemin case of error - Return 409 ('Requested form type is not allowed')
Service logic
Define template id
Get Composition by id from ME
Get template id from configuration based on Composition.type and form_type:
COMPOSITION_{{Composition.type}}_{{form_type}}_TEMPLATE_ID (ex. COMPOSITION_ADOPTION_INFO_CERTIFICATE_TEMPLATE_ID)
Prepare request parameters for MAN based on mapping bellow
Add
display
for codeable concept elements where it says enrich with display valueGet dictionary value by dictionary key from corresponding dictionary
Set dictionary value as coding[].display for this element
Call Render Template(MAN) to render printout form
Return response with generated pdf to the client
Print form mapping
MAN Request parameter | Source value |
---|---|
Сomposition | Select Composition from ME by id = composition_id from the request |
Composition.type | ME.composition.type (enrich with display value) |
Composition.category | ME.composition.category (enrich with display value) |
Composition.date | ME.composition.date (cast datetime to date only) |
Composition.title | ME.composition.title |
Composition.event | ME.composition.event[].code (enrich ME.composition.event[].code with display value) |
Composition.extension | ME.composition.extension (enrich composition.extension[].code, enrich composition.extension[].valueCodeableConcept.coding[].code with display value) |
Employee | Select Employee from PRM by id = Composition.attester.[0].party.identifier.value |
Employee.id | PRM.employee.id |
Employee.position | PRM.employee.position (enrich with display value) |
Party | Select Party from PRM by id = Employee.party_id |
Party.last_name | PRM.party.last_name |
Party.first_name | PRM.party.first_name |
Party.second_name | PRM.party.second_name |
Legal_entity | Select Legal Entity from PRM by id = Composition.custodian.identifier.value |
Legal_entity.name | PRM.legal_entity.name |
Legal_entity.edrpou | PRM.legal_entity.edrpou |
Person | Select Person from MPI by id = patient_id from request |
Person.id | Person.id |
Person.last_name | PRM.person.last_name |
Person.first_name | PRM.person.first_name |
Person.second_name | PRM.person.second_name |
Person.tax_id | PRM.person.tax_id |
Person.unzr | PRM.person.unzr |
Person.birth_date | PRM.person.birth_date |
Print form examples
ЕСОЗ - публічна документація