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.
- ITSM for Healthcare and Hospitals
- Data model and migration order
The tables behind ITSM for Healthcare and Hospitals
ITSM for Healthcare and Hospitals ships with 53 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
- 53
- Features
- 7, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Service work:
Services, Incidents, incident updates, incident response events, service requests and Problems connect operating work to a named service.
Clinical consequence:
Clinical service impacts and clinical downtime register link care impact and outage timing to Incidents.
Change control:
Changes, clinical change advisory reviews, clinical system deployments and clinical rollback checks hold a planned change, advisory decision, service deployment and change rollback check for review.
Equipment:
Assets, biomedical assets, biomedical asset assignments, biomedical asset service links and biomedical asset disposals track device identity, custody and dependencies.
Guidance and inbound evidence:
Clinical knowledge articles, clinical article feedback and integration receipts preserve reviewed guidance and event processing outcomes.
Every table, by feature
- Clinical incidents6
- Service requests3
- Changes and deployments5
- Biomedical assets7
- Downtime and impact4
- Integration receipts1
- Problems and knowledge5
- Shared and settings32
- Incidents
Clinical system incidents with priority, assignment and resolution state.
Linked to Services, Assets, People - Incident response events
Response Events records for IT service and asset operations.
Linked to Incidents, People - Incident updates
Chronological updates recorded against a clinical incident.
Linked to Incidents, People - Clinical service impacts
Clinical Service Impacts records for IT service and asset operations.
Linked to Incidents, People - Services
Clinical and IT services delivered across the hospital and health system.
Linked to People - Assets
Tracked clinical, network and endpoint devices in service.
Linked to Services
- Service requests
Clinical service requests raised by hospital staff.
Linked to People, Services - Services
Clinical and IT services delivered across the hospital and health system.
Linked to People - People
People records for IT service and asset operations.
Linked to Users
- Changes
Clinical system changes with risk, schedule and rollback plan.
Linked to Services - Clinical change advisory reviews
CAB Reviews records for IT service and asset operations.
Linked to Changes, People - Clinical system deployments
Deployments records for IT service and asset operations.
Linked to Services - Clinical rollback checks
Rollback Checks records for IT service and asset operations.
Linked to Changes - Services
Clinical and IT services delivered across the hospital and health system.
Linked to People
- Assets
Tracked clinical, network and endpoint devices in service.
Linked to Services - Biomedical assets
Biomedical Assets records for IT service and asset operations.
Linked to Assets - Biomedical asset assignments
Asset Assignments records for IT service and asset operations.
Linked to Assets, People - Biomedical asset service links
Asset Service Links records for IT service and asset operations.
Linked to Assets, Services - Biomedical asset disposals
Asset Disposals records for IT service and asset operations.
Linked to Assets, People - Services
Clinical and IT services delivered across the hospital and health system.
Linked to People - People
People records for IT service and asset operations.
Linked to Users
- Clinical service impacts
Clinical Service Impacts records for IT service and asset operations.
Linked to Incidents, People - Clinical downtime register
Register Outages records for IT service and asset operations.
Linked to Incidents - Incidents
Clinical system incidents with priority, assignment and resolution state.
Linked to Services, Assets, People - People
People records for IT service and asset operations.
Linked to Users
- Integration receipts
Inbound clinical integration events and their processing outcome.
- Problems
Recurring or underlying problems behind clinical incidents.
Linked to Services, People - Clinical knowledge articles
Knowledge Articles records for IT service and asset operations.
Linked to People, Services - Clinical article feedback
Article Feedback records for IT service and asset operations.
Linked to Clinical knowledge articles - Incidents
Clinical system incidents with priority, assignment and resolution state.
Linked to Services, Assets, People - Services
Clinical and IT services delivered across the hospital and health system.
Linked to People
Keys and references
Use stable service, asset and person identifiers before importing transactions. Keep the external event identifier and payload hash on each integration receipt. Link impact and downtime to the original incident. Retain the change review row and its reviewer when recording the implementation result. Check device tags against the original asset before importing assignments.
Migration order
- Load Users, People and Services, then confirm the intended owner references.
- Load Assets and biomedical assets, followed by assignments and service links.
- Load Incidents and linked response events, updates, clinical impacts and downtime records.
- Load service requests, Problems and Changes; then load advisory reviews, service deployments and rollback checks.
- Load knowledge articles and integration receipts, then reconcile identifiers and permissions before the pilot.
Set up ITSM for Healthcare and Hospitals your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.