This is a good use case for Power Platform, but I would treat it as a workflow coordination layer rather than a replacement for an EHR/EMR.
For this type of patient transport and discharge coordination, Dataverse can work well if the data model is kept clean from the beginning. I would separate the main records instead of putting everything into one large table.
A practical structure could look something like this:
-
Patient table: basic patient reference details only, ideally with the minimum required data
-
Transport Request table: pickup location, destination, transport type, requested time, priority, required equipment, current status
-
Discharge/Readiness table: clinical readiness, paperwork status, medication instructions, nurse confirmation, physician sign-off
-
Department table: nursing, case management, billing, dispatch, admin
-
Vendor/Transport Provider table: internal transport, ambulance provider, non-emergency transport provider
-
Approval table: insurance approval, billing review, authorization status, notes, timestamp
-
Trip Status/Trip Log table: assigned driver/vendor, ETA, arrived, delayed, completed, cancelled
-
Communication/Activity Log table: key updates, alerts sent, status changes, user comments
The important part is to make the transport request the central operational record. Each request can then link to patient reference data, readiness status, vendor assignment, approvals, and trip updates.
For alerts, Power Automate would be useful for events such as:
-
Patient marked ready but no transport assigned
-
Transport request waiting for approval for too long
-
Vehicle/driver assigned but discharge paperwork still incomplete
-
ETA changed
-
Trip delayed
-
Request cancelled or rescheduled
-
High-priority transfer created
I would be careful not to over-automate every status change though. In hospital workflows, too many alerts can quickly become noise. It is better to define a few meaningful triggers that require action.
For role-based access, I would keep it role-specific:
-
Nurses: update patient readiness and discharge status
-
Case managers: create transport requests and manage discharge coordination
-
Billing: update approval/authorization status
-
Dispatch: assign vendor/driver and update trip status
-
Admin/leadership: reporting and oversight
-
External vendors: limited access only, preferably through a controlled portal or integration layer
For EHR/EMR integration, I would avoid making Power Platform the source of truth for clinical records. The safer approach is usually to store only the operational data needed for transport coordination and reference the EHR patient/encounter IDs where required. Any integration should be reviewed carefully for security, privacy, audit logging, and compliance requirements.
A few lessons I would keep in mind:
-
Start by mapping the current discharge and transport workflow before building tables.
-
Define status values clearly, because vague statuses like “pending” create confusion.
-
Use audit/history tracking for important changes.
-
Keep PHI exposure as limited as possible.
-
Build dashboards around exceptions, not just total trip volume.
-
Make mobile access simple for dispatch or transport staff if they are updating trip progress.
-
Test with real-world delay scenarios, not just the happy path.
Overall, Power Platform can be a good fit for this if the scope is patient movement coordination, approvals, dispatch visibility, and operational tracking. For anything deeper involving clinical decision-making or complete medical record management, it should integrate with the EHR rather than try to replace it.
