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
- Data model
The tables behind Healthcare CRM
Healthcare CRM ships with 10 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 10
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Organization and Accounts
Organizations owns Accounts and team members. Team members.User connects membership to Users. Accounts stores contact name, Address and eligibility note for the counterparty.
Opportunity Pipeline
Opportunities references Organization, Owner and Counterparty. Record number identifies the relationship; Status, expected close date and expected value USD describe its commercial state.
Relationship Activity
Relationship activities uses Parent to reference Opportunities and retains line number, Revision, due at, completed at and Outcome.
Referral Follow Ups
Referral follow ups references both Organization and Parent. Its Status and Revision sit beside referral code, received at, follow up due and consent basis.
Review and Evidence
Record attachments references Parent and uploaded by; review decisions references Parent and Reviewer and records source revision and operation key.
Operation Reconciliation
Operation receipts references Parent and records expected revision, result state, effect references and failure reason for the guarded action.
Every table, by feature
- Organization and Accounts4
- Opportunity Pipeline7
- Relationship Activity3
- Referral Follow Ups6
- Review and Evidence6
- Operation Reconciliation6
- Organizations
Healthcare organizations that own accounts, opportunities and referral follow-ups.
- Accounts
Eligible active counterparty accounts within an organization.
Linked to Organizations - Team members
Authenticated platform identities with an organization role scope.
Linked to Organizations, Users - Users
Users
Linked to Users
- Opportunities
Relationship opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Accounts
Eligible active counterparty accounts within an organization.
Linked to Organizations - Team members
Authenticated platform identities with an organization role scope.
Linked to Organizations, Users - Relationship activities
Qualification, proposal and outcome activity evidence for an opportunity.
Linked to Opportunities - Record attachments
Uploaded evidence files linked to an opportunity with a visibility scope.
Linked to Opportunities, Team members - Review decisions
Independent review decisions recorded against a source revision.
Linked to Opportunities, Team members - Operation receipts
Stable operation receipts recording guarded action outcomes and effects.
Linked to Opportunities
- Relationship activities
Qualification, proposal and outcome activity evidence for an opportunity.
Linked to Opportunities - Opportunities
Relationship opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Operation receipts
Stable operation receipts recording guarded action outcomes and effects.
Linked to Opportunities
- Referral follow ups
Nonclinical referral follow-up extensions routed through independent review.
Linked to Organizations, Opportunities - Opportunities
Relationship opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Organizations
Healthcare organizations that own accounts, opportunities and referral follow-ups.
- Review decisions
Independent review decisions recorded against a source revision.
Linked to Opportunities, Team members - Record attachments
Uploaded evidence files linked to an opportunity with a visibility scope.
Linked to Opportunities, Team members - Operation receipts
Stable operation receipts recording guarded action outcomes and effects.
Linked to Opportunities
- Record attachments
Uploaded evidence files linked to an opportunity with a visibility scope.
Linked to Opportunities, Team members - Review decisions
Independent review decisions recorded against a source revision.
Linked to Opportunities, Team members - Opportunities
Relationship opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Referral follow ups
Nonclinical referral follow-up extensions routed through independent review.
Linked to Organizations, Opportunities - Team members
Authenticated platform identities with an organization role scope.
Linked to Organizations, Users - Operation receipts
Stable operation receipts recording guarded action outcomes and effects.
Linked to Opportunities
- Operation receipts
Stable operation receipts recording guarded action outcomes and effects.
Linked to Opportunities - Opportunities
Relationship opportunities with lifecycle, expected value and expected close date.
Linked to Organizations, Team members, Accounts - Referral follow ups
Nonclinical referral follow-up extensions routed through independent review.
Linked to Organizations, Opportunities - Review decisions
Independent review decisions recorded against a source revision.
Linked to Opportunities, Team members - Relationship activities
Qualification, proposal and outcome activity evidence for an opportunity.
Linked to Opportunities - Record attachments
Uploaded evidence files linked to an opportunity with a visibility scope.
Linked to Opportunities, Team members
Keys and references
Use the actual reference identifiers when matching records. A contact name or opportunity subject is display context and should not substitute for a reference. Organization codes and account codes help people reconcile an import with their source lists.
Resolve the current user through team members.User before comparing Opportunities.Owner with that team member. Review decisions.Parent points to Opportunities. When a decision concerns a referral follow ups record, verify the exact child and revision through the guarded action’s operation key and effect evidence.
The Users table includes a User reference to Users. Preserve this reference structure and resolve its actual platform identity mapping during migration. Do not replace it with an invented identity field. Expected value USD remains denominated in USD independently of Organizations.Currency.
Migration order
- Organizations and identities. Establish Organizations and existing platform Users, resolving the User reference with the platform’s identity handling.
- Membership and counterparties. Link team members and Accounts to their organization; check active scope and account eligibility.
- Opportunities. Resolve Organization, Owner and Counterparty before importing relationship stages and expected values.
- Activities and referrals. Link relationship activities and referral follow ups to their parent opportunity; preserve source dates and revisions.
- Evidence and decisions. Link record attachments and review decisions to their source records and real actors. Preserve historical decision reasons.
- Operation receipts. Import only genuine action evidence with its original keys, revisions and references. Check that the declared effects can be traced.
Set up Healthcare CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.