/
Service request autoexpiration

ЕСОЗ - публічна документація

Service request autoexpiration

Overview

Service request auto-expiration process starts periodically based on the value of configuration parameter SERVICE_REQUESTS_AUTOEXPIRATION_SCHEDULE. It cancels all service requests in status Active that have an expiration date less than the current time.

Process

  1. Update 

    1. status = recalled

    2. status_reason = autoexpired

    3. status history

           for all service requests where:

  • status = active

  • current_time < expiration_date (inserted_at + SERVICE_REQUEST_EXPIRATION_DAYS (365 days on Prod))

  • program_processing_status= NULL or new

  • there is no encounter or diagnostic report in ME where incoming_referral/based_on reference service_request

  • If the service request is based on the activity with quantity:

    1. Recalculate and set remaining_quantity for the activity as described at PreQualify Service Request | Validate service request

Related content

Service Request Dictionaries and configurable parameters
Service Request Dictionaries and configurable parameters
Read with this
RC_REHAB_Service request autoexpiration+
RC_REHAB_Service request autoexpiration+
More like this
Create Service Request
Create Service Request
Read with this
RC_REHAB_Service request status model+
RC_REHAB_Service request status model+
More like this
Перевірка та взяття в обробку направлення за програмою медичним закладом
Перевірка та взяття в обробку направлення за програмою медичним закладом
Read with this
RC_REHAB_[AUTO] Terminate Medication Request+
RC_REHAB_[AUTO] Terminate Medication Request+
More like this

ЕСОЗ - публічна документація