{"id":14543,"date":"2025-07-07T14:02:22","date_gmt":"2025-07-07T14:02:22","guid":{"rendered":"https:\/\/training.nuth-itt.co.uk\/?page_id=14543"},"modified":"2025-07-07T14:10:28","modified_gmt":"2025-07-07T14:10:28","slug":"medisight-regenerating-failed-documents","status":"publish","type":"page","link":"https:\/\/training.nuth-itt.co.uk\/?page_id=14543","title":{"rendered":"mediSIGHT – Regenerating Failed Documents"},"content":{"rendered":"

\"\"<\/h1>\n

mediSIGHT – Regenerating Failed Documents<\/h1>\n
How to resolve a failed document generation in mediSIGHT<\/div>\n

This guide details how to resolve a document that failed to generate in mediSIGHT.\u00a0 This may be noted within the application itself, or via the automated Interface with DocStore.<\/p>\n

<\/i> This guide is to be used for the sole purpose of rectifying Failed Documents.\u00a0 It must not be used for correcting clinical details once encounters are locked.<\/div>\n

Failed to generate errors need to be resolved as soon as possible, as the information within the document is not available to any clinician whilst the document has failed.<\/p>\n

Failed Document Generation in mediSIGHT<\/strong><\/p>\n

\"\"<\/p>\n

Failed Document Generation Alert from DocStore Interface<\/strong><\/p>\n

\"\"<\/p>\n

Resolving Failed Document Generation<\/div>\n
    \n
  1. Open mediSIGHT<\/li>\n
  2. Find the patient affected<\/li>\n
  3. Click “Events”<\/li>\n
  4. Locate the failed encounter<\/li>\n
  5. Identify the failed document, and whether it is an encounter (clinical documentation) or a letter<\/li>\n
  6. Identify if the failed document is locked<\/li>\n
  7. Follow the appropriate Section Guide below.\n
      \n
    1. Not generated letter, or letter failed; not locked<\/a><\/li>\n
    2. Not generated letter, or letter failed; locked<\/a><\/li>\n
    3. Generated letter; not locked<\/a><\/li>\n
    4. Generated letter; locked<\/a><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      \"\"<\/p>\n

      (1) Encounter has not generated a letter, or the letter failed, and it is not locked<\/div>\n
        \n
      1. Click the Pencil icon<\/li>\n
      2. If mediSIGHT asks whether to Refresh sections, click “Proceed without refreshing”<\/li>\n<\/ol>\n

        \"\"<\/p>\n

          \n
        1. Click Finalise<\/li>\n
        2. Confirm the document is received into DocStore (this can take up to 5 minutes)<\/li>\n<\/ol>\n

          \"\"<\/p>\n

          (2) Encounter has not generated a letter, or letter failed, but it is locked<\/div>\n
            \n
          1. Click the Padlock icon and confirm the action<\/li>\n<\/ol>\n

            \"\"<\/p>\n

            <\/i> Unlocking encounters can only be performed by system administrators.\u00a0 Please contact Mr Cunningham, Mandy Partridge or IT Service Desk for assistance<\/div>\n
              \n
            1. Click the Pencil icon<\/li>\n
            2. Click Finalise<\/li>\n
            3. Confirm the document is received into DocStore (this can take up to 5 minutes)<\/li>\n<\/ol>\n
              (3) Encounter generated a letter, but it is not locked<\/div>\n
              <\/i> “Is not locked” means that the encounter has not yet been auto-locked by mediSIGHT.\u00a0 This is only true on the same day that the encounter was documented.\u00a0 Unlocking an encounter, does not change it to the state of “Is not locked” for the purposes of this document.<\/div>\n
                \n
              1. Click the pencil icon<\/li>\n
              2. If mediSIGHT asks whether to Refresh sections, click “Proceed without refreshing”<\/li>\n<\/ol>\n

                \"\"<\/p>\n

                  \n
                1. Click Finalise<\/li>\n
                2. If mediSIGHT asks whether to regenerate the letter, click “Load previous version”<\/li>\n<\/ol>\n

                  \"\"<\/p>\n

                    \n
                  1. Once the letter has loaded, click “e-sign and action all”<\/li>\n<\/ol>\n

                    \"\"<\/p>\n

                      \n
                    1. Confirm that the encounter note and letter have been received into DocStore (this can take up to 5 minutes)<\/li>\n<\/ol>\n
                      (4) Encounter generated a letter, and it is locked<\/div>\n
                      <\/i> Letters are automatically exported from mediSIGHT to the external print service (Synertec) at midnight on the day of the documentation.<\/p>\n

                      Letters can be stopped in Prism by authorised users until 4pm on the working day after the documentation was made.\u00a0 Following this the physical copies of the letters have already entered the postal system and cannot be stopped.<\/p>\n

                      Care must be taken when editing locked encounters that generate a letter to prevent duplicate copies entering the postal service.<\/div>\n

                        \n
                      1. Click the Padlock icon and confirm the action<\/li>\n<\/ol>\n

                        \"\"<\/p>\n

                        <\/i> Unlocking encounters can only be performed by system administrators.\u00a0 Please contact Mr Cunningham, Mandy Partridge or IT Service Desk for assistance<\/div>\n
                          \n
                        1. Complete the steps in the previous section\u00a0“(3) Encounter generated a letter, but it is not locked”<\/strong><\/em><\/li>\n
                        2. If it was the letter itself that had failed to generate, no further action is required and the letter will now be processed and sent in the postal system.<\/li>\n
                        3. If it was the encounter that had failed to generate, but the letter had generated, then a duplicate letter has just been generated and action will be required:\n