Purpose

API paragraph not found

Specification

...

Link

...

https://medicaleventsmisapi.docs.apiary.io/#reference/medical-events/diagnostic-report-data-package/submit-diagnostic-report-package

...

Resource

...

/api/patients/{{id}}/diagnostic_report_package

...

Scope

...

diagnostic_report:write

...

Components

...

Diagnostic Report Data Package

...

Microservices

...

API paragraph not found

...

Protocol type

...

REST

...

Request type

...

POST

...

Sync/Async

...

Async

...

Public/Private/Internal

...

Public

Logic

API paragraph not found

Request structure

See on Apiary

Example:

{
  "signed_data": "'ew0KICAicGVyaW9kIjogew0KIC...'"
}

Authorize

1. Verify the validity of access token

   1. in case of error return 401 ('Access denied')

2. Check user scope diagnostic_report:write in order to perform this action

   1. in case of error generate 403 response ('Invalid scopes')

Request to process the request using a token in the headers

Headers

Наприклад:

• Content-Type:application/json

• Authorization:Bearer mF_9.B5f-4.1JqM

Request data validation

Request validation

DS validation

1. DS must be valid

2. The document must be signed by recorder

   1. Select PRM.parties.tax_id from PRM where PRM.parties.id ==( Select  PRM.employees.party_id where PRM.employees.id==$.diagnostic_report.recorded_by.identifier.value)

   2. ds.drfo == select a

      1. in case of error retuert 409 "Document must be signed by the recorder of the diagnostic_report"

3. Recorder must be a current user

   1. $.diagnostic_report.recorded_by.identifier.value is one of current user's employee

      1.  in case of error return 409 "Document must be sent by the recorder of the diagnostic_report"

Validate Legal Entity Type

Validate legal entity from token: legal_entities.type should be in me_allowed_transactions_le_types and legal_entities.status =='active' 

Diagnostic report validation

1. Validate diagnostic_report _id is unique for MongoDB.Diagnostic_reports

2. Validate that one of diagnostic reports category corresponds to service category, that is references as code in DR

   1. $.diagnostic_report.category[?]=PRM.services.category where PRM.services.id=$.diagnostic_report.code.identifier.value

      1. in case of error return 422 "None of the diagnostic report categories matches with the service category"

3. Validate that service, referenced as a code in DR, is active
   Note. For diagnostic_report.code pass only "service", and the "service_group" does not pass

   1. PRM.services.is_active = true where PRM.services.id=$.diagnostic_report.code.identifier.value

      1. in case of errror return 422 "Service is not active"

   2. If service_requests.code.identifier.value is service, validate $diagnostic_report.code.identifier.value = service_requests.code.identifier.value

      1. in case error return 409, "Service in diagnostic_report differ from service in service request"

   3. if service_requests.code.identifier.value is service_group, validate $diagnostic_report.code.identifier.value in (SELECT service_id from service_inclusions where service_group_id='service_requests.code.identifier.value')

      1. in case error return 409, "Service in diagnostic_report differ from services in service request's service_group"

   4. if request_allowed==false return error 422 "Request is not allowed for this service"

4. Validate referrals

   1. As a referral it can be referenced electronic (registered in the system) OR paper service request

   2. Validate ($.diagnostic_report.based_on OR $.diagnostic_report.paper_referral) or none in request

   3. Validate based on as Reference

   4. Validate paper referral as Object (paper_referral)

   5. Validate that service_request, referenced as based_on, is

      1. in status is active or program_processing_status=in_progress (any status is valid in case program_processing_status= in_progress)

         1. in case of error return 409 "Invalid service request status"

      2. used_by_legal_entity==token.client_id OR null

         1. in case of error return 409 "Service request is used by another legal_entity"

      3. if program is defined than used_by_legal_entity==token.client_id or NULL

         1. in case of error return 409 "Service request is used by another legal_entity"

      4. if program is defined than program_processing_status == new, in_queue or in_progress

      5. check that service_request contains based_on parameter

         1. in case based_on present in service_request

            1. verify care_plan:

               1. It should be in active status

               2. Care plan's period end (if exist) should be greater than current date or equal.

            2. verify activity:

               1. It has activity.detail.kind=service_request; activity.detail.product_reference=service_id. 

               2. It has scheduled, in_progress status

         2. in case based_on not present in request skip previous validations.

5. Validate effective_period as a period (PeriodValidation)

6. Validate that issued is within acceptable limits

   1. $.diagnostic_reports[*].issued<= current date_time

      1. in case of error 422 "Issued date  must be in past"

   2. $.diagnostic_reports[*].issued>=current_date-diagnostic_report_max_days_passed

      1. in case of error 422 "Issued must be greater than  {{current_date-diagnostic_report_max_days_passed}}" 

7. Validate recorded_by as Employee:

   1. recorded_by employee_types allowed: DOCTOR, SPECIALIST, ASSISTANT, LABORANT

      1. in case of error 422 "Invalid employee type"

8. Validate performer.identifier as Employee:

   1. check that performer.identifier field is mandatory and employee_types allowed: DOCTOR, SPECIALIST, ASSISTANT, LABORANT

      1. in case of error 422 "Invalid employee type"

9. Validate managing_organization is a current legal_entity

   1. $.managing_organization.identifier.value==token.client_id

      1. in case of error 409 "Managing organization does not correspond to user's legal entity."

10. Validate results_interpreter.identifier as Employee:

    1. if the category.coding.code is in (imaging, diagnostic_procedure) check that results_interpreter.identifier is an employee with employee_type = DOCTOR or SPECIALIST

       1. in case of error 422 "Invalid employee type"

    2. if the category.coding.code is in (diagnostic_curative, laboratory_procedure) - results_interpreter field is optional and the results_interpreter.identifier validation skipped

11. Validate only One of the fields is filled:

    1. $.diagnostic_report[*].results_interpreter.reference OR $.diagnostic_report[*].results_interpreter.text

    2. $.diagnostic_report[*].performer.reference OR $.diagnostic_report[*].performer.text

12. Validate division

    1. Validate division as Reference(Referencevalidation)

    2. $division is an existing ID in PRM.divisions

       1. in case return 422, "Division with such id is not found"

    3. division.status=ACTIVE and is_active=true

       1. in case error return 409, "Division is not active"

    4. division.legal_entity_id = $client_id

       1. in case error return 409, "Division is not in current legal_entity"

13. Patient must be active

    1. check that patients.status == active

       1. in case patients.status == inactive

          1. check mpi.persons(or mpi.prepersons if patients.preperson == true).updated_at and validate that now() - updated_at<=SUBMIT_DIAGNOSTIC_REPORT_PACKAGE_ALLOWED_PERIOD_MINUTES configuration (in minutes)

             1. in case of error return 409 (Person is not active more that the allowed time for data submitting)

14. Validate patient verification status:

    1. If diagnostic report has based_on with valid and active service request, then skip this validation.

    2. Else check patient's verification_status is not equal to NOT_VERIFIED.

       1. in case of error return 409, "Patient is not verified"

15. Validate patient

    1. check that patients.status == active

       1. in case of error return 409 (Person is not active)

Observation validation

...

Validate observations ids as  primary keys (Primarykeyvalidation)

...

Validate that diagnostic_report of ALL observation is a current DR

1. $.observations[*].diagnostic_report.identifier.value==$.diagnostic_report.id

   1. in case of error return "Submitted diagnostic report is not allowed for the observation"

...

$.observations[*].effective_period validate as Period PeriodValidation

...

Validate that the date is within acceptable limits

1. $.observations[*].issued <= current_time

   1. in case of error return "Issued date must be in past"

2. $.observations[*].issued>=current_date-observation_max_days_passed

   1. in case of error "Issued must be greater than  {{current_date-observation_max_days_passed}}"

...

Validate performer as Employee:

1. performer employee_types allowed: DOCTOR, SPECIALIST, ASSISTANT, LABORANT

   1. in case of error 422 "Invalid employee type"

...

Validate $.observations[*].value_period as a Period

...

Validate component

1. $.observations[*].components[*].value_period as a Period

...

Related care plan validation

1. in case service request has reference on care plan and diagnostic report has reference on service request check possibility to create diagnostic report depending on service_request[].activity remaining quantity

   1. calculate the quantity of artifacts that are contained in the request and have a link to the service request. Compare remaining_quantity from activity with the quantity of artifacts. Check that difference is greater then or equal to zero

      1. in case of error return 409 "The total amount of the prescribed service quantity exceeds quantity in care plan activity"

Validate $.observations.code

if observations.code.coding[*].code value is included in chart variables 'OBSERVATION_CODES_WITH_<VALUE_TYPE>_REQUIRED', <value_type> field is mandatory

...

Purpose

Using this web service you can submit Diagnostic Report Package

Specification

Logic

Using this web service you can submit:

Global and configurable parameters

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/907837561/Variables#Medical-Events

Request structure

See on Apiary

Example:

{
  "signed_data": "'ew0KICAicGVyaW9kIjogew0KIC...'"
}

Authorize

1. Verify the validity of access token

   1. in case of error return 401 ('Access denied')

2. Check user scope diagnostic_report:write in order to perform this action

   1. in case of error generate 403 response ('Invalid scopes')

3. If BLOCK_UNVERIFIED_PARTY_USERS is true, then check party's data match following condition: verification_status != NOT_VERIFIED or (verification_status = NOT_VERIFIED and updated_at <= current_date - UNVERIFIED_PARTY_PERIOD_DAYS_ALLOWED):

   1. in case not match - return 403 ("Access denied. Party is not verified")

Request to process the request using a token in the headers

Headers

Наприклад:

• Content-Type:application/json

• Authorization:Bearer mF_9.B5f-4.1JqM

Request data validation

Request validation

DS validation

1. DS must be valid

2. The document must be signed by recorder

   1. Select PRM.parties.tax_id from PRM where PRM.parties.id ==( Select  PRM.employees.party_id where PRM.employees.id==$.diagnostic_report.recorded_by.identifier.value)

   2. ds.drfo == select a

      1. in case of error retuert 409 "Document must be signed by the recorder of the diagnostic_report"

3. Recorder must be a current user

   1. $.diagnostic_report.recorded_by.identifier.value is one of current user's employee

      1.  in case of error return 409 "Document must be sent by the recorder of the diagnostic_report"

Validate Legal Entity Type

Validate legal entity from token: legal_entities.type should be in me_allowed_transactions_le_types and legal_entities.status =='active' 

Diagnostic report validation

1. Validate diagnostic_report _id is unique for MongoDB.Diagnostic_reports

2. Validate that one of diagnostic reports category corresponds to service category, that is references as code in DR

   1. $.diagnostic_report.category[?]=PRM.services.category where PRM.services.id=$.diagnostic_report.code.identifier.value

      1. in case of error return 422 "None of the diagnostic report categories matches with the service category"

3. Validate that service, referenced as a code in DR, is active
   Note. For diagnostic_report.code pass only "service", and the "service_group" does not pass

   1. PRM.services.is_active = true where PRM.services.id=$.diagnostic_report.code.identifier.value

      1. in case of errror return 422 "Service is not active"

   2. If service_requests.code.identifier.value is service, validate $diagnostic_report.code.identifier.value = service_requests.code.identifier.value

      1. in case error return 409, "Service in diagnostic_report differ from service in service request"

   3. if service_requests.code.identifier.value is service_group, validate $diagnostic_report.code.identifier.value in (SELECT service_id from service_inclusions where service_group_id='service_requests.code.identifier.value')

      1. in case error return 409, "Service in diagnostic_report differ from services in service request's service_group"

   4. if request_allowed==false return error 422 "Request is not allowed for this service"

4. Validate referrals

   1. As a referral it can be referenced electronic (registered in the system) OR paper service request

   2. Validate ($.diagnostic_report.based_on OR $.diagnostic_report.paper_referral) or none in request

   3. Validate based on as Reference

   4. Validate paper referral as Object (paper_referral)

   5. Validate that service_request, referenced as based_on, is

      1. in status is active or program_processing_status=in_progress (any status is valid in case program_processing_status= in_progress)

         1. in case of error return 409 "Invalid service request status"

      2. used_by_legal_entity==token.client_id OR null

         1. in case of error return 409 "Service request is used by another legal_entity"

      3. if program is defined than used_by_legal_entity==token.client_id or NULL

         1. in case of error return 409 "Service request is used by another legal_entity"

      4. if program is defined than program_processing_status == new, in_queue or in_progress

      5. check that service_request contains based_on parameter

         1. in case based_on present in service_request

            1. verify care_plan:

               1. It should be in active status

               2. Care plan's period end (if exist) should be greater than current date or equal.

            2. verify activity:

               1. It has activity.detail.kind=service_request; activity.detail.product_reference=service_id. 

               2. It has scheduled, in_progress status

               3. For an old activities (has no units in quantity) validate remaining_quantity as described at Submit Encounter Data Package: Related care plan validation

         2. in case based_on not present in request skip previous validations.

      6. Check if service request quantity is not exhausted as described at Submit Encounter Data Package: Related service request validation

5. Validate effective_period as a period (PeriodValidation)

6. Validate that issued is within acceptable limits

   1. $.diagnostic_reports[*].issued<= current date_time

      1. in case of error 422 "Issued date  must be in past"

   2. $.diagnostic_reports[*].issued>=current_date-diagnostic_report_max_days_passed

      1. in case of error 422 "Issued must be greater than  {{current_date-diagnostic_report_max_days_passed}}" 

7. Validate recorded_by as Employee:

   1. recorded_by employee_types allowed: DOCTOR, SPECIALIST, ASSISTANT, LABORANT

      1. in case of error 422 "Invalid employee type"

8. Validate performer.identifier as Employee:

   1. check that performer.identifier field is mandatory and employee_types allowed: DOCTOR, SPECIALIST, ASSISTANT, LABORANT

      1. in case of error 422 "Invalid employee type"

9. Validate managing_organization is a current legal_entity

   1. $.managing_organization.identifier.value==token.client_id

      1. in case of error 409 "Managing organization does not correspond to user's legal entity."

10. Validate results_interpreter.identifier as Employee:

    1. if the category.coding.code is in (imaging, diagnostic_procedure) check that results_interpreter.identifier is an employee with employee_type = DOCTOR or SPECIALIST

       1. in case of error 422 "Invalid employee type"

    2. if the category.coding.code is in (diagnostic_curative, laboratory_procedure) - results_interpreter field is optional and the results_interpreter.identifier validation skipped

11. Validate only One of the fields is filled:

    1. $.diagnostic_report[*].results_interpreter.reference OR $.diagnostic_report[*].results_interpreter.text

    2. $.diagnostic_report[*].performer.reference OR $.diagnostic_report[*].performer.text

12. Validate division

    1. Validate division as Reference(Referencevalidation)

    2. $division is an existing ID in PRM.divisions

       1. in case return 422, "Division with such id is not found"

    3. division.status=ACTIVE and is_active=true

       1. in case error return 409, "Division is not active"

    4. division.legal_entity_id = $client_id

       1. in case error return 409, "Division is not in current legal_entity"

13. Patient must be active

    1. check that patients.status == active

       1. in case patients.status == inactive

          1. check mpi.persons(or mpi.prepersons if patients.preperson == true).updated_at and validate that now() - updated_at<=SUBMIT_DIAGNOSTIC_REPORT_PACKAGE_ALLOWED_PERIOD_MINUTES configuration (in minutes)

             1. in case of error return 409 (Person is not active more that the allowed time for data submitting)

14. Validate patient verification status:

    1. If diagnostic report has based_on with valid and active service request, then skip this validation.

    2. Else check patient's verification_status is not equal to NOT_VERIFIED.

       1. in case of error return 409, "Patient is not verified"

15. Validate patient

    1. check that patients.status == active

       1. in case of error return 409 (Person is not active)

16. Validate for each element in specimens array, if submitted:

    1. Check the element is a Reference on a specimen resource

       1. in case of error return 422 “not allowed in enum”

    2. Check it exists in DB and belongs to the same patient:

       1. in case of error return 422 "Specimen not found"

    3. Check status is available

       1. in case of error return 422 "Invalid specimen status"

Observation validation

1. Validate observations ids as  primary keys (Primarykeyvalidation)

2. Validate that diagnostic_report of ALL observation is a current DR

   1. $.observations[*].diagnostic_report.identifier.value==$.diagnostic_report.id

      1. in case of error return "Submitted diagnostic report is not allowed for the observation"

3. $.observations[*].effective_period validate as PeriodValidation

4. Validate that the date is within acceptable limits

   1. $.observations[*].issued <= current_time

      1. in case of error return "Issued date must be in past"

   2. $.observations[*].issued>=current_date-observation_max_days_passed

      1. in case of error "Issued must be greater than  {{current_date-observation_max_days_passed}}"

5. Validate performer as Employee:

   1. performer employee_types allowed: DOCTOR, SPECIALIST, ASSISTANT, LABORANT

      1. in case of error 422 "Invalid employee type"

6. Validate $.observations[*].value_period as a Period

7. Validate component

   1. if $.observations[*].code.coding[*].system is "eHealth/ICF/classifiers":

      1. Check number of component items with $.observations[*].components[*].code.coding[*].system = "eHealth/ICF/qualifiers": 

         1. if $.observations[*].code.coding[*].code starts from "b" letter, then components must contain exact 1 item with:

            1. $.observations[*].components[*].code.coding[*].code = "extent_or_magnitude_of_impairment" 

               1. in case of missing qualifier - return 422 "Missing components with qualifiers <list of missing qualifiers>"

               2. in case of incorrect number of qualifiers - return 422 "Required 1 component, but got <number of items>"

               3. in case value is not active in dictionary - return 422 "Value is not active"

         2. if $.observations[*].code.coding[*].code starts from "s" letter, then components must contain exact 3 items with:

            1. $.observations[*].components[*].code.coding[*].code = "extent_or_magnitude_of_impairment"

            2. $.observations[*].components[*].code.coding[*].code = "nature_of_change_in_body_structure"

            3. $.observations[*].components[*].code.coding[*].code = "anatomical_localization"

               1. in case of missing qualifier - return 422 "Missing components with qualifiers <list of missing qualifiers>"

               2. in case of incorrect number of qualifiers - return 422 "Required 3 components, but got <number of items>"

               3. in case value is not active in dictionary - return 422 "Value is not active"

         3. if $.observations[*].code.coding[*].code starts from "d" letter, then components must contain exact 2 items with:

            1. $.observations[*].components[*].code.coding[*].code = "performance"

            2. $.observations[*].components[*].code.coding[*].code = "capacity"

               1. in case of missing qualifier - return 422 "Missing components with qualifiers <list of missing qualifiers>"

               2. in case of incorrect number of qualifiers - return 422 "Required 2 components, but got <number of items>"

               3. in case value is not active in dictionary - return 422 "Value is not active"

         4. if $.observations[*].code.coding[*].code starts from "e" letter, then components must contain exact 1 item with:

            1. $.observations[*].components[*].code.coding[*].code = "barrier_or_facilitator"

               1. in case of missing qualifier - return 422 "Missing components with qualifiers <list of missing qualifiers>"

               2. in case of incorrect number of qualifiers - return 422 "Required 1 component, but got <number of items>"

               3. in case value is not active in dictionary - return 422 "Value is not active"

      2. Check $.observations[*].components[*].value_codeable_concept is present in each item with $.observations[*].components[*].code.coding[*].system = "eHealth/ICF/qualifiers" and  $.observations[*].components[*].value_codeable_concept.coding[*].system corresponds to $.observations[*].components[*].code.coding[*].code

         1. in case not present or doesn't correspond return 422 "Doesn't correspond to $.observations[i].components[i].code"

         2. in case code value is not active in dictionary - return 422 "Value is not active"

   2. $.observations[*].components[*].value_period as a  Period

8. Related care plan validation

   1. in case service request has reference on care plan and diagnostic report has reference on service request check possibility to create diagnostic report depending on service_request[].activity remaining quantity

      1. calculate the quantity of artifacts that are contained in the request and have a link to the service request. Compare remaining_quantity from activity with the quantity of artifacts. Check that difference is greater then or equal to zero

         1. in case of error return 409 "The total amount of the prescribed service quantity exceeds quantity in care plan activity"

9. Validate $.observations.code

   1. if observations.code.coding[*].code value is included in chart variables 'OBSERVATION_CODES_WITH_<VALUE_TYPE>_REQUIRED', <value_type> field is mandatory

      1.  in case of error return 422 “This field is required for code = <code>“

   2. if observations[*].code.coding[*].system is "eHealth/ICF/classifiers", then:

      1. Check observations[*].categories[*].coding[*].system should contain "eHealth/ICF/observation_categories"

         1. in case of error return 422 “Code doesn't match observation category“

      2. Check observations[*].components are presented

         1. in case of error return 422 “Components required“

10. Validate $.observations[*].categories

    1. is an array with only one item

       1. in case of error return 422 "Expected a maximum of 1 items but got <number of elements>"

    2. $.observations[*].categories[*].coding[*].system is "eHealth/observation_categories" or "eHealth/ICF/observation_categories" 

       1. in case of error return 422 "Value is not allowed in enum"

    3. $.observations[*].categories[*].coding[*].code corresponds to the system

       1. in case of error return 422 "Value is not allowed in enum"

    4. If $.observations[*].categories[*].coding[*].system = "eHealth/ICF/observation_categories", then $.observations[*].code should be filled from "eHealth/ICF/classifiers" dictionary.

       1. in case of error return 422 “Code doesn't match observation category“

11. Validate specimen, if submitted:

    1. Check the field is a Reference on a specimen resource

       1. in case of error return 422 “not allowed in enum”

    2. Check it exists in DB and belongs to the same patient:

       1. in case of error return 422 "Specimen not found"

    3. Check status is available

       1. in case of error return 422 "Invalid specimen status"

Processing

API paragraph not found

...

{
  "data": {
    "status": "pending",
    "eta": "2018-08-02T10:45:16.000Z",
    "links": [
      {
        "entity": "job",
        "href": "/Jobs/NBXk9EyErUZv1RhXgyvgg"
      }
    ]
  },
  "meta": {
    "code": 202,
    "url": "http://example.com/resource",
    "type": "object",
  }  "request_id": "req-adasdoijasdojsda"
 ]  }
},

{
  "meta": {
    "code": 

...

404,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-

...

adasdoijasdojsda"
  },
  "error": {
    "type": "NOT_FOUND",
    "message": "Patient not found"
  }
}

...

{
  "meta": {
    "code": 404,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  },
  "error": {
    "type": "NOT_FOUND",
    "message": "Patient not found"
  }
}

Post-processing processes

Set managing_organization for submitted observations

...

ME.conditions{cond_id}.managing_organization=token.client_id.

...

in case service request has reference on care plan and diagnostic report.based_on was filled set $.diagnostic_report.id to related to $.service_request $.activity[].outcome_reference

...

Update $ .activity.status to in_progress if previous activity status was scheduled

...

Post-processing processes

Set managing_organization for submitted observations

1. ME.conditions{cond_id}.managing_organization=token.client_id.

2. in case service request has reference on care plan and diagnostic report.based_on was filled set $.diagnostic_report.id to related to $.service_request $.activity[].outcome_reference

3. Update $ .activity.status to in_progress if previous activity status was scheduled

4. Update the $ .activity.remaining_quantity parameter by subtracting the quantity of artifacts that have a reference on service request that contains an $.based_on.[]activity

5. Update the $ .activity.remaining_quantity parameter by the value achieved at Submit Encounter Data Package: Related care plan validation (for an old activities only that has no quantity units)

6. Update remaining_quantity in the service request with a value that was calculated in the Submit Encounter Data Package: Related service request validation

7. Change specimens status to unavailable for referenced specimens. Also, set status_reason for a specimen: system = specimen_invalidate_reasons, code = used.

8. Set origin_episode (if $.based_on in request and $.based_on.service_request.context != null) for Diagnostic Report:

   1. origin_episode is an object from the $.service_request.context.episode

HTTP status codes

...