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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

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

  • No labels