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.
- Blood Donation Management
- Data Model
The tables behind Blood Donation Management
Blood Donation Management ships with 15 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
- 15
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Donor Registry
Donors holds identity, consent status and screening authority. Record attachments links donor evidence, version, signature and expiry details through Donor.
Team Access
Team members links each staff identity to Users through User. Clinical privileges and care team assignments refer to team members through Clinician; each assignment also refers to Donors.
Collection Operations
Donations links Donor and Owner, with scheduled at, started at, ended at, visit type and Status describing the collection.
Blood Unit Processing
Blood units and laboratory tests reference Donations through Donation. Laboratory tests also names authorized by in team members.
Review and Follow-up
Review decisions references Donation and Reviewer. Operation receipts references Donor and assigned to, with dates and Status for the follow-up action.
Custody and Charges
Custody events and Charges reference Donation. Payments references Donor. Exchange rates supplies read-only effective rates as a separate reference source.
Every table, by feature
- Donor Registry2
- Team Access4
- Collection Operations3
- Blood Unit Processing3
- Review and Follow-up4
- Custody and Charges5
- Donors
Donor identity and consent status
Linked to Team members - Record attachments
Signed evidence documents linked to a donor
Linked to Donors
- Team members
Blood bank team members and their platform identities
Linked to Users - Users
Users
Linked to Users - Clinical privileges
Professional privileges and their verification state
Linked to Team members - Care team assignments
Care team access assignments and their effective period
Linked to Donors, Team members
- Donations
Screened collections and their recorded interval
Linked to Donors, Team members - Donors
Donor identity and consent status
Linked to Team members - Blood units
Collected blood units and their processing state
Linked to Donations
- Blood units
Collected blood units and their processing state
Linked to Donations - Laboratory tests
Laboratory test results recorded against a donation
Linked to Donations, Team members - Donations
Screened collections and their recorded interval
Linked to Donors, Team members
- Review decisions
Review decisions recorded against a donation
Linked to Donations, Team members - Operation receipts
Follow-up operation receipts and their result state
Linked to Donors, Team members - Donations
Screened collections and their recorded interval
Linked to Donors, Team members - Donors
Donor identity and consent status
Linked to Team members
- Custody events
Custody events recorded against a donation
Linked to Donations, Team members - Charges
Service charges for donations
Linked to Donations - Payments
Payments received and their confirmation state
Linked to Donors - Exchange rates
Read-only effective exchange rates for this app.
- Donations
Screened collections and their recorded interval
Linked to Donors, Team members
Keys and references
The model contains 15 tables. Most records expose Id; exchange rates uses ID. Blood units.record number and Donors.donor code are human-facing identifiers. Resolve reference values to their actual target records during migration rather than joining people by their display names.
Team members.User connects a staff record to a platform user. Users.User is also a required reference to Users; confirm the account creation sequence before migrating staff. Resolve current-user views through the team members.User link when their source field targets team members.
Laboratory tests and custody events link at donation level. Charges belongs to a donation, while Payments belongs to a donor. Preserve those distinctions when grouping records. Avoid duplicating a donor payment when joining it to several donations or charges.
Migration order
- Resolve account identities. Establish Users and their required User references through the account setup process.
- Prepare the team. Import team members with valid User references, then clinical privileges with the correct Clinician.
- Identify donors. Import Donors with screening authority, then care team assignments and record attachments.
- Load collections. Import Donations with Donor and Owner before blood units, laboratory tests, custody events, review decisions and Charges.
- Load donor follow-up and receipts. Import operation receipts and Payments with their Donor references; resolve assigned to for follow-up work.
- Check reference rates. Review the read-only exchange rates source separately from the financial entries and preserve its effective dates.
Set up Blood Donation Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.