These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Healthcare CRM
- Features
- Review and Evidence
Review and Evidence
Put supporting files and independent decisions beside the opportunity they explain.
OverviewInternal Evidence Library×
Healthcare CRM · Review and Evidence
New
Internal Evidence Library
Record attachments
| Title | Evidence type | Parent | File | Uploaded at | Uploaded by | |
|---|---|---|---|---|---|---|
| Internal ra-384 | ET-713 | OPP-37556 | FLE-277 | 08 Oct | ||
| Internal ra-875 | ET-302 | OPP-53665 | FLE-270 | 21 Oct | ||
| Internal ra-951 | ET-794 | OPP-39885 | FLE-639 | 27 Oct | ||
| Internal ra-536 | ET-654 | OPP-44518 | FLE-109 | 22 Oct | ||
| Internal ra-276 | ET-482 | OPP-15715 | FLE-212 | 13 Oct |
6 of 6 records
Internal ra-384Record attachments · RA-30616
InternalEvidence typeET-713
ParentOPP-37556
FileFLE-277
Uploaded at08 Oct
What you can do
Review the version that will be acted on
A Sales Manager needs enough evidence to make a decision and enough context to know what that decision authorizes. The opportunity holds the relationship. Its attachments carry supporting files, while the decision history records the reviewer, reason and source revision. The Relationship Owner prepares the material; the reviewer evaluates the specific work presented.
This matters when a proposal changes after a discussion or a referral follow-up needs correction. An earlier approval may describe a different version of the work. Keeping the source revision with the decision gives the team a way to distinguish an approved case from a later change that still needs attention.
How the work is organized
- Evidence files. Record a title, evidence type and file against the opportunity. The upload date and uploading team member help a reviewer identify the material and establish who supplied it.
- Visibility. Set the evidence visibility to Internal or Shared according to the customer’s access policy. Review that policy with the App Administrator before treating an attachment as appropriate for a wider audience.
- Decision history. The Sales Manager records Approve, Reject or Return with a reason and decision time. The source revision and operation key connect the decision to the action being reviewed.
What to agree during setup
Agree what evidence supports each decision. A customer outcome may need an acceptance document or a clear loss explanation supported by the relationship activity. A referral decision needs the referral evidence and the correct organization context. Use titles and evidence types that make the relevant file easy to identify during a busy review.
Define how an independent reviewer is selected and how a preparer responds to a Return decision. Decide who checks attachment visibility before the team shares material through any connected system. The Shared label must be interpreted through the agreed access policy; it does not by itself identify a recipient or establish a delivery channel.
Check the handoff on an actual case
Rehearse an opportunity with a proposal attachment and a later acceptance attachment. The Relationship Owner supplies meaningful titles and evidence types. The Sales Manager opens the current opportunity revision, reads the relevant activity and records the reason for the outcome decision.
Change the opportunity before the completion action and ask the reviewer to explain whether the earlier decision still covers the changed version. It should require a fresh check of the affected work. For a referral decision, follow the recorded effect references and operation key back to the intended follow-up so that another referral on the same opportunity cannot borrow its approval. Have the Auditor repeat that trace without editing anything.
What your team sees
- Internal Evidence Library — Internal supporting files with the uploader and parent relationship visible.
- Decision Register — Decisions organized with their source revision, reviewer and recorded reason.
- Referral Review Queue — Submitted referral work that needs an independent decision.
Follow the work through
See referral review and completion and customer outcome review. Review the access rehearsal on the roles page.
What it keeps track of
Data model- Record attachments
- Uploaded evidence files linked to an opportunity with a visibility scope.
- Review decisions
- Independent review decisions recorded against a source revision.
- Opportunities
- Relationship opportunities with lifecycle, expected value and expected close date.
- Referral follow ups
- Nonclinical referral follow-up extensions routed through independent review.
- Team members
- Authenticated platform identities with an organization role scope.
- Operation receipts
- Stable operation receipts recording guarded action outcomes and effects.
Who uses it
Permissions- Relationship Owner
- Supplies evidence.
- Sales Manager
- Makes the independent decision.
- Auditor
- Follows the evidence trail; App Administrator maintains the membership context used for access.
Set up Healthcare CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.