All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

ITSM for Healthcare and Hospitals · Available now

Healthcare IT service management for clinical systems.

A hospital IT team records an incident against the affected service and, when relevant, an asset. Capture acknowledges the incident and records a first response event.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen Clinical Incidents
ITSM for Healthcare and Hospitals · Incidents

Open Clinical Incidents

Incidents in one list

New incident
Incidents in view
6
Low
2
Medium
2
High
1
Low2
INC-CLIN-2026-0412Restore medication scanner pairing
07 Nov
AST-BIO-2026-0231Restore patient registration queue
25 Nov
Add
Medium2
CHG-CLIN-2026-0138Patch radiology image gateway
11 Nov
KBA-CLIN-2026-0116Refresh bedside monitor gateway
18 Nov
Add
High1
REQ-CLIN-2026-0721Investigate delayed lab results
24 Nov
Add
Critical1
PRB-CLIN-2026-0084Replace emergency unit switch
09 Nov
Add
INC-CLIN-2026-0412Incidents · INC-84553
Low
SummaryRestore medication scanner pairing
StatusOpen
Opened at07 Nov
ServiceMedication administration
Assigned toDivya Patel
Review changeINC-84553 · INC-CLIN-2026-0412

Change Advisory Reviewer decides the clinical change review and records the reason.

Waiting for Change Advisory Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
53
Saved views
15
Roles with set permissions
8
Reports and dashboards
8
Features

Clinical work in view

Every feature works on the same records. Pick one to see the screen your team works in.

Clinical incidents

Keep clinical service interruptions assigned and traceable.

  • Triage
  • Response
  • Care impact
  • Incidents
  • Incident response events
  • Incident updates
  • Clinical service impacts
  • Services
  • Assets
Explore clinical incidents
OverviewMy Clinical Incidents
ITSM for Healthcare and Hospitals · Clinical incidents

My Clinical Incidents

Incidents

New
IdSummaryPriorityStatusOpened atService
INC-CLIN-2026-0412Restore medication scanner pairingLowOpen25 NovClinical lab results
CHG-CLIN-2026-0138Patch radiology image gatewayMediumAcknowledged23 NovClinical lab results
REQ-CLIN-2026-0721Investigate delayed lab resultsHighInvestigating21 NovBedside device connectivity
PRB-CLIN-2026-0084Replace emergency unit switchCriticalResolved21 NovBedside device connectivity
AST-BIO-2026-0231Restore patient registration queueLowClosed06 NovBedside device connectivity
6 of 6 records
INC-CLIN-2026-0412Incidents · INC-27789
Low
SummaryRestore medication scanner pairing
StatusOpen
Opened at25 Nov
ServiceClinical lab results
Example screen with sample data
Process

From interruption to outcome

Clinical incident to verified outcome ships ready to use. One step needs a named approval before the work moves on: Review change (Change Advisory Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Capture incident

    Record the affected clinical service, priority and responder.

    INC-CLIN-2026-0412INC-84553 · Clinical Service Desk Analyst
    Capture incidentBy Clinical Service Desk Analyst
  2. Acknowledge response

    Review the first response event and take ownership of the next action.

    INC-CLIN-2026-0412INC-84553 · Incident Responder
    Acknowledge responseBy Incident Responder
  3. Investigate impact

    Link updates and patient care impact to the incident.

    INC-CLIN-2026-0412INC-84553 · Incident Responder
    Investigate impactBy Incident Responder
  4. Review change

    Have the advisory reviewer record the decision and reason.

    INC-CLIN-2026-0412INC-84553 · Change Advisory Reviewer
    Review changeBy Change Advisory Reviewer
    ApprovalChange Advisory Reviewer decides the clinical change review and records the reason.
  5. Record deployment

    Track implementation against the planned clinical change.

    INC-CLIN-2026-0412INC-84553 · Clinical Change Manager
    Record deploymentBy Clinical Change Manager
  6. Resolve incident

    Record the restoration outcome for manager review.

    INC-CLIN-2026-0412INC-84553 · Incident Responder
    Resolve incidentBy Incident Responder
Inside a record

Linked service and device context

Open any incident to see its clinical service impacts, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Summary, Status, Opened at and Service.

  2. 2
    Clinical service impacts

    Each line is linked to this incident.

  3. 3
    Who works on it

    Clinical Service Desk Analyst, Incident Responder and Biomedical Engineer, each with their own permissions.

  4. 4
    Process stages

    Capture incident and Acknowledge response, with the role that acts.

  5. 5
    Approvals

    Review change, with who decides.

Open Clinical IncidentsINC-CLIN-2026-0412
ITSM for Healthcare and Hospitals · Incidents

INC-CLIN-2026-0412

Restore medication scanner pairing · Low

Log activity
1
Record details
SummaryRestore medication scanner pairing
StatusOpen
Opened at07 Nov
ServiceMedication administration
2
Clinical service impacts

INC-CLIN-2026-0412

IdClinical servicePatient care impact
INC-CLIN-2026-0412Electronic health recordDelayed
CHG-CLIN-2026-0138Medication administrationUnavailable
REQ-CLIN-2026-0721Radiology image accessDelayed
Clinical service impacts
6
3

Who works on it

  • Clinical Service Desk AnalystManage Incidents, incident updates, service requests
  • Incident ResponderManage Incidents, incident response events, incident updates…
  • Biomedical EngineerManage Assets, biomedical assets, biomedical asset assignments…
4

Process stages

  • Capture incidentClinical Service Desk Analyst
  • Acknowledge responseIncident Responder
5

Approvals

  • Review changeChange Advisory Reviewer
    Approved
Example screen with sample data
Approvals

Decisions with a named reviewer

OverviewApprovals
ITSM for Healthcare and Hospitals · Overview

Approvals

Signed in as Change Advisory Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • SR-71938INC-CLIN-2026-0412
    Clinical account accessRequested by Minseo Park
    Submitted1dActions
  • SR-63118CHG-CLIN-2026-0138
    Bedside device supportRequested by Elias Haddad
    Submitted1dActions
  • SR-55042REQ-CLIN-2026-0721
    Workstation replacementRequested by Francesca Moretti
    Submitted5dActions
  • SR-64279PRB-CLIN-2026-0084
    EHR role changeRequested by Divya Patel
    Submitted6dActions

Who approves what

DecisionApprover
Review changeHave the advisory reviewer record the decision and reason.Change Advisory Reviewer
1 approval rule · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens ITSM for Healthcare and Hospitals to the work that is theirs. Pick a role to see what it starts with.

Clinical Service Desk Analyst

Receives hospital staff requests and clinical incidents and keeps the initial record current.

This is the first screen this role sees.

OverviewOpen Clinical Incidents

Open Clinical Incidents

Incidents · Clinical Service Desk Analyst

Low2
INC-CLIN-2026-0412Restore medication scanner pairing
07 Nov
AST-BIO-2026-0231Restore patient registration queue
25 Nov
Add
Medium2
CHG-CLIN-2026-0138Patch radiology image gateway
11 Nov
KBA-CLIN-2026-0116Refresh bedside monitor gateway
18 Nov
Add
High1
REQ-CLIN-2026-0721Investigate delayed lab results
24 Nov
Add
Critical1
PRB-CLIN-2026-0084Replace emergency unit switch
09 Nov
Add
Example screen with sample data
Reports

Questions answered from records

Review incident timing, care impact, requests, changes and inbound events.

Overview
ITSM for Healthcare and Hospitals · Overview

ITSM for Healthcare and Hospitals dashboard

This quarter

Changes in view
6
Low
2
Medium
2
High
2

Incidents by status

How far records got this quarter

StageReachedStep
Open44
Acknowledged2659%
Investigating1869%
Resolved1161%

Number of incidents by status

Sample counts per stage

900
40Open
30Acknowledged
70Investigating
90Resolved
50Closed
Example screen with sample data
  1. 01Incident state and priority

    Group clinical incidents by Status and Priority for the service queue.

  2. 02Acknowledgment and resolution intervals

    Compare opened at with acknowledged at and resolved at for each incident.

  3. 03Clinical care impact

    Group patient care impact by clinical service and linked Incident.

  4. 04Request due dates and completion

    Compare due at and completed at by service requests Status and Service.

  5. 05Change risk and decisions

    Review Changes Risk with linked clinical change advisory reviews Decision.

  6. 06Biomedical service dependencies

    Group biomedical asset service links by Service and Asset, with verified at.

  7. 07Integration processing outcomes

    Count integration receipts by Provider and Status using received at.

  8. 08Recurring problem state

    Review Problems by Service, Status and Owner.

Controls

Traceable clinical handoffs

Each stage of clinical incident to verified outcome names the role that acts and the status it records, so a change is never anonymous.

OverviewClinical incident to verified outcome
ITSM for Healthcare and Hospitals · Process

Clinical incident to verified outcome

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
5
Tables touched
11
Capture incident
Clinical Service Desk Analyst
StatusOpen → Acknowledged
RecordsIncident response events, Incidents, Services
Investigate impact
Incident Responder
StatusAcknowledged → Investigating
RecordsClinical service impacts, Incident updates, Incidents
Review changeApproval
Change Advisory Reviewer, Clinical Change Manager
StatusDraft → Review
RecordsClinical change advisory reviews, Changes
Clinical incident to verified outcome
  1. Start
    Capture incidentOpen → Acknowledged
    Incident response events
  2. Step
    Investigate impactAcknowledged → Investigating
    Clinical service impacts
  3. Approval
    Review changeDraft → Review
    Clinical change advisory reviews
  4. Step
    Schedule approved changeReview → Approved
    Changes
  5. Step
    Record deploymentApproved → Implementing
    Clinical system deployments
Example screen with sample data
AI agent

Prepare work with Proto

Prepare clinical IT work and review decisions with Proto.

It can

  • Incident Responder: List open incidents by priority and show their latest attributed update.
  • Service Manager: Compare request due dates with completion times for a named service.
  • Clinical Change Manager: Gather the scheduled window, risk, rollback plan and advisory decision for a change.
  • Biomedical Engineer: Find assigned devices with an upcoming service due date and their linked service.

Stays with a person

  • The change advisory reviewer makes the approval decision and records a reason.
  • The clinical owner confirms patient care impact and restoration.
  • The service manager reviews the completed handoff.
  • Proto may organize the relevant records for those people, subject to their access, but it does not replace their judgment or the connected system’s observed outcome.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • ITSM for Healthcare and Hospitals
  • Clinical applications
  • Monitoring
  • Identity provider
  • Deployment platform
  • Biomedical source
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 53 tables
53tables
  • Clinical incidents6
  • Service requests3
  • Changes and deployments5
  • Biomedical assets7
  • Downtime and impact4
  • Integration receipts1
  • Problems and knowledge5
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the service boundary

    Choose a clinical service, its owner, devices and the people who make incident and change decisions.

  2. Map source records

    Reconcile service identifiers, asset tags, people and external event identifiers. Keep historical dates and prior outcomes intact.

  3. Configure a bounded pilot

    Set up incident handling, care impact, staff requests and the clinical change review for one service.

  4. Rehearse exceptions

    Work a delayed care impact, rejected receipt, overdue request and deferred change with the people responsible.

  5. Review and release

    Compare the recorded outcome with source events, check permissions and obtain the service and clinical owners’ acceptance.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for ITSM for Healthcare and Hospitals.

All questions
How do I get started?

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.

How does an incident reach the responder?

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.

Where does patient care impact go?

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

Can we track biomedical equipment?

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

How is a clinical change reviewed?

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

What happens to a rejected integration event?

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

How do staff requests close?

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

Can we bring existing records?

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

What determines cost?

The pricing page explains platform use and metered work. Scope implementation around the services and connections in your 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.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appITSM for Healthcare and Hospitals

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.