Questions, answered

Click Get started, then use Proto to configure ITSM for Healthcare and Hospitals for your business. Pilot one clinical service with its incident responders, devices, request queue and change reviewers.

The incident records its assigned person, service, priority and state. Capture applies acknowledgment and records the first response event. The responder begins investigation and adds an attributed update.

A linked clinical service impact record identifies the affected care service, impact, clinical owner and downtime procedure attachment.

Assets hold the tag, serial number, location, status and service. Biomedical records add the device identifier, department, clinical criticality and service due date.

The change records risk, scheduled window and rollback plan. An advisory review holds the reviewer’s decision and reason before implementation.

Its receipt retains the provider, external identifier, receive time, payload hash and rejected status for reconciliation with the source owner.

A request carries a requester, service, due date and state. Its completion date lets the service manager review the result against the due date.

Map stable service, device, person and external event identifiers first. Rehearse a small import and compare linked records and dates before expanding.

The pricing page explains platform use and metered work. Scope implementation around the services and connections in your pilot.