Skip to content
  1. Home
  2. Our work

Bayer

Bayer radiology: a paper workflow rebuilt in Power Apps

We moved a radiology workflow at Bayer off paper forms, spreadsheets and phone calls and into an app built on Microsoft Power Platform. The average time from request to completed report fell from 8 days to 3.

Industry
Pharma and life sciences / Radiology
Platform
Microsoft Power Platform
Stage
Delivered
  • 8 → 3 days

    Average time from request to completed report

  • Every workflow action logged for compliance reviews

  • Power Apps, Power Automate, Dataverse and Power BI

The challenge

The challenge

Requests arrived on paper forms and were scheduled on spreadsheets and whiteboards. Anyone who wanted to know where a request stood had to phone or email.

Approach

A workflow that ran on paper

Bayer's radiology team had modern imaging equipment, but the work around it was still mostly on paper. Requests came in on paper forms. Technicians planned sessions on spreadsheets and whiteboards, and reports written on paper had to be typed into digital systems by hand.

Tracking a request meant phone calls and emails. When a compliance review came up, the audit trail had to be pieced together from paper records.

Large radiology information systems existed, but they were built for hospitals. They were expensive to license and to run, and they fit this team's workflow poorly. Bayer wanted a tool that matched its own process and that its own staff could maintain.

One app for requests, scheduling and reports

Staff now submit requests in a Power Apps app instead of on paper. The app will not accept an incomplete request. It routes each request to the right imaging modality and tells the radiology team as soon as it arrives.

Every request moves through the same stages: submitted, scheduled, in progress, completed and reported. The status changes as staff finish each step, and everyone involved can see it in the app, so the calls and emails asking for status stopped.

Technicians schedule from a view that shows the equipment, staff availability and the priority of each request, and the app suggests a slot. Reports are written in the app from templates for common study types and stored with the request.

Built on Power Platform, connected to the systems already there

The whole solution runs on Microsoft Power Platform. Power Apps provides the screens and the workflow, and Power Automate sends the notifications and runs the integrations. The data sits in Dataverse, and the dashboards are in Power BI.

The app works alongside the existing systems instead of replacing them. Staff sign in with their existing Active Directory accounts, and finished reports go into the enterprise document management system automatically.

Managers now see request volumes, average completion times, equipment use and bottlenecks in Power BI. None of that was visible while the process ran on paper.

Designed with the people who use it

The people who work with the app every day joined the design team from the start. We tested several prototypes with them and changed the app after each round, so the screens follow how the team already thinks about its work and little training was needed.

Every action in the workflow is logged: who submitted a request, when the work was done, who reviewed the report and what changed. The audit trail is ready whenever a compliance review asks for it, and we kept refining the app after launch based on how people used it.

Inside the implementation

Architecture overview

The workflow runs on Microsoft Power Platform. Power Apps holds the screens and the stages of each request, Power Automate carries notifications and integrations, Dataverse stores the data and Power BI shows the dashboards. Existing systems stay in place.

Radiology request workflow

  1. 01

    Request

    Staff submit a request in the app instead of on a paper form.

    • Power Apps
    • Completeness checks
    • Routing to the right modality
    Next: Scheduled work
  2. 02

    Schedule and track

    Each request moves through set stages, and its status changes as staff finish each step.

    • Scheduling view
    • Stage tracking
    • Power Automate notifications
    Next: Completed work
  3. 03

    Report and store

    Reports are written from templates and stored with the request.

    • Report templates
    • Dataverse
    • Enterprise document management
    Next: Oversight
  4. 04

    Oversight

    Managers see volumes, completion times and bottlenecks.

    • Power BI dashboards
    • Audit trail

Sign-in and access

Staff sign in with their existing Active Directory accounts.

Audit trail

The app logs who submitted each request, when the work was done, who reviewed the report and what changed.

Logical view of the documented architecture. Client-specific infrastructure and identifiers are omitted.

Key design decisions

  1. Work alongside the existing systems

    The app connects to the document management system and the company directory instead of replacing them, which kept disruption low.

  2. Make status a result of the work

    Status changes when staff complete a step, so nobody has to report it separately and nobody has to ask for it.

  3. Design with the people who use it

    Prototypes were tested with the team and changed after each round, so the screens follow the way the team already works.

How the workflow fits together

  1. A request enters the app

    The app accepts it only when it is complete, routes it and notifies the radiology team.

  2. The work is scheduled

    Technicians pick a slot from a view of equipment, staff availability and priority, with a suggestion from the app.

  3. The report is written and filed

    The report is written from a template and goes to the document management system automatically.

  4. Managers review the flow

    Power BI shows volumes, completion times and bottlenecks, and the audit trail is ready for compliance reviews.

Questions for a similar implementation

Use these review points when you assess this architecture for your own environment.

  • Which steps of the current paper process carry a compliance requirement?
  • Which existing systems must the app read from or write to?
  • Who on the team will maintain the app after launch?

Results

The outcome

The average time from request to completed report fell from 8 days to 3. Every step is logged for compliance reviews, and managers see volumes and bottlenecks in Power BI.

Stack

Technology used

  • Microsoft Power Apps
  • Power Automate
  • Dataverse
  • Power BI
  • Active Directory

First published on our blog on 12 May 2025.

Research paper

Compliance-grade RAG: Retrieval systems a regulator can audit

How to build retrieval that a regulated reviewer can trust and audit.

Read the paper
Get the designed PDF

Start with your workflow.

We define the scope and acceptance criteria with you, in writing, before the build starts. Wider programs are scoped separately, and commercial terms are set in the statement of work.

  • Built to SOC 2, HIPAA and GDPR standards
  • EU AI Act-aligned delivery
  • Microsoft Solutions Partner