Unfortunately, this is not sufficient to fully meet the customer's requirements. This option has already been offered to the customer and is partially in practice, as far as I know. However, the customer desires a specific functionality akin to an "oops factor" or a timer, which would allow them to modify the report within a defined period after approval. One potential "solution" could be the implementation of a new status, such as "timer," which would indicate that the report is in a temporary state (with a timer). The report status would then only be set to "finalized" after the timer has expired, providing the necessary window for changes.
We don't have that so called "oops-factor" implemented currently but it is possible at least to delay the transmission of reports/acc. items via HL7 for a certain period via HL7 configuration. Wouldn't that maybe partly answer the customer's request (assumging that they can take back approval and do changes before the delay passed)?
Unfortunately, this is not sufficient to fully meet the customer's requirements. This option has already been offered to the customer and is partially in practice, as far as I know. However, the customer desires a specific functionality akin to an "oops factor" or a timer, which would allow them to modify the report within a defined period after approval. One potential "solution" could be the implementation of a new status, such as "timer," which would indicate that the report is in a temporary state (with a timer). The report status would then only be set to "finalized" after the timer has expired, providing the necessary window for changes.
We don't have that so called "oops-factor" implemented currently but it is possible at least to delay the transmission of reports/acc. items via HL7 for a certain period via HL7 configuration. Wouldn't that maybe partly answer the customer's request (assumging that they can take back approval and do changes before the delay passed)?