Why can the patient not see a report or images?
Images and the report are decided separately. A person can see images and still not see the report.
- Find the study and open the panel, as on the find page.
- Read the image outcome and the report outcome, and the reason under each.
- If you have View as patient, open the patient record, write a reason, and choose View as patient. That list is what they can open. It does not sign them in, and a report that is not released does not show the report text.
A delay
A held result with a reason such as site delay not yet elapsed, or referrer-first delay not yet elapsed, is waiting. The panel shows the time it becomes releasable when there is one. The hours come from the site rule, or the practice default when the site has no rule. Policies is where an admin reads those hours. A modality or procedure rule can keep its own hours.
Waiting on referrer acknowledgement stays held until the referrer has acknowledged, if that rule applies. A preliminary report stays held unless the winning policy allows preliminary reports. No report yet, or report not finalised, means there is nothing final to show.
Reports switched off for a clinic
If the report reason is "Reports for this clinic are shared by your doctor.", written reports are switched off for that site or brand. Reports whose normal release time is after the switch-off are held. A report that was already due at that moment stays on the normal clock. Images keep releasing unless a deny rule for that procedure also hides images.
A site row replaces the brand row for that site. Patients are not shown your staff note.
An admin switches reports off by choosing the brand or one site, setting Reports off from, optionally writing a staff note, and choosing Switch reports off. Retire turns that row off. From the next page load, later reports follow the normal delay again. An equal release time stays visible. Reports the patient can already see stay visible.
Release early does not override this switch-off. The dialog opens, but Release early stays off and names the restriction. The source-permission tick does not override it either. To show reports again for the clinic, retire the control. An allow code for one procedure keeps the usual delay for that code. A deny code blocks that procedure's report even when reports are on, and hides images only when that box is ticked.
A hold you placed
A manual hold is the strongest decision. It beats a release. The reason starts with manual hold. Remove it from the active override. See the hold page.
A patient flag, including a medico-legal hold
If the reason says the patient is flagged, the result is blocked for every target. A medico-legal hold is this kind of block. Release early cannot override it, and neither can a source exception. The flags that block release are listed on the winning policy under Policies. This console does not edit the flag. Correct it in Karisma after you have verified identity.
The same hard block covers a procedure the policy never releases, a patient under the age gate, and a missing date of birth when an age gate applies. The dialog says to resolve the restriction. Do not keep pressing Release early.
The clinical source has not allowed the portal
If the reason says portal access is not permitted by the clinical source, Karisma has not allowed this study on the portal. An admin can tick the source exception on Release early for that one study and the current source version. The tick is recorded with the reason. It does not turn the clinic back on, and it does not override a manual hold, a patient flag, a blocked procedure, or reports switched off.
If the reason says the study has not been reconciled with the clinical source, or patient release is disabled for the source, do not release over it. Ask an admin. Releasing is not how you investigate a feed.
Images are missing
Released images still need a copy. If the study says images are not available yet, the decision can be released while the pictures are still on the way. Do not tell the patient the images are lost. Imaging worklist is a separate queue for matching a copy. It is not covered step by step here.