Page Comparison

...

1. Only authenticated and authorized users with appropriate scope can invoke Qualify Device Request

2. This method returns for existing Device Request the result of data validation within each submitted medical program, but not creates any entities in the system.

3. Each Medical program may have its unique conditions for the Device Dispense. They can be based on analysis of personal info, device definition list, terms, locations and combinations of them.

4. Any Medical program can have separate block of branching logic configured at medical program settings /wiki/spaces/CSI/pages/17467605147 by NHS administrator.

5. Сompatibility is checked only for programs which are available in payload (array).

6. Successful invocation of the method returns decision for each program if it is valid or not to create Device dispense with submitted combination of parameters in the payload. If program is invalid, the reason must be returned in the response.

7. Allowed for existing and active Device Requests

8. Also medical program provision is checked for the division of the pharmacy.

...

• Check that there is no other IN_PROGRESS device dispenses based on the same device request

  • Find all device dispenses related to the same device request ($.based_on)

  • Check that there are no records in status IN_PROGRESS where wheninserted_handed_overat + config device_dispense_ttl >= current date-time()

    • in case of error - return 422 "Other active device dispense already exist."

...

1. If general error found at Validate division section, that doesn’t depend on medical program, then return corresponding error code with error message

2. If general validation passed, then collect array for all programs in payload with status for each (VALID or INVALID) and rejection_reason

3. For each program return a list of appropriate Device Definitions found at Validate Device Definitions step

4. Generate response according to specification