Skip to content
Unit 2 of 18
RFPLumen DiagnosticsOpen anytime - every module Task uses this brief

Case study appendix — Lumen Diagnostics

Contents · 6

This is the case for every module Task (Modules 2–11). It is written as a request for proposal, so it also doubles as a worked example of the genre. The capstone uses a different customer; do not reuse the artefacts you produce here.

This organisation is invented. Any resemblance to a real business is coincidental. The numbers are illustrative, not a description of any real market. Where a module's worked example needs a figure the case does not give (named users, record counts, unit costs), it states that figure as its own assumption — do the same in your answers.


Business context

Lumen Diagnostics operates a private diagnostic-imaging network: 180 imaging centres across four regions, working alongside roughly 600 independent partner radiology practices that take overflow and specialist studies.

Referrals arrive from clinics and physicians. Each referral must become an appointment at either a Lumen centre or a partner practice, matched on modality, urgency, patient location and price.

FactValue
Studies performed per year4.2 million
Referrals received per operating day~14,000 (about 300 operating days a year, so roughly one study per referral)
Imaging centres180, across 4 regions
Partner practices~600
Current approachLargely manual — phone and email between the referral desk, patients, centres and partner practices

The manual process is the problem: it consumes referral-desk time, leaves partner capacity unused because nobody can see it, and produces no reliable utilisation data.


Project overview

Lumen wants to engage a Supplier to build a scheduling platform, delivered as a service and hosted and supported by the Supplier. It must become the single source of truth for imaging appointments, giving the referral desk, partner practices and patients a shared view of confirmed bookings.

Lumen is open to recommendations on system design to meet the objective. The Supplier should meet the requirements cost-efficiently.

Six aspects the system must account for — these are effectively the business drivers:

AspectRequirement
Cost reductionCentralised utilisation and financial reporting for day-to-day management and budgeting
AutomationRemove the existing manual scheduling and confirmation steps
IntegrationIntegrate with the existing referral management system, the patient identity service, and corporate single sign-on
ConsistencyOne coherent look, feel and process across every portal
FlexibilityA highly configurable solution that can support Lumen's growth
PerformanceSustain peak demand, and cope with disruption events such as a centre outage or a regional surge

Functional requirements

Note as you read that several of these are written the way customers actually write them — loosely. Making them measurable is the Module 3 exercise.

AreaRequirement
Availability search and prioritisationIntelligent search across partner practice availability and manually uploaded slots, based on the referral's requirements. Prioritisation on clinical match plus custom rules set by the Scheduling Manager in the Administration Portal. Referral requirements originate in the referral management system and may be amended by the patient in the Patient Portal or by the Scheduling Manager. Prioritisation may change over time as rules change
Offer and confirmation workflowSupport the stages Requested → Triaged → Offered → Accepted/Declined → Confirmed → Completed → Billed, with email and SMS notification on stage change. Must allow the workflow to be changed and extended later. Alongside automated offers, support manual booking by the referral desk, capturing all details through web forms
Change managementFrequent synchronisation with the referral management system. New referrals, amendments and cancellations are driven by those updates. Conflicts merged according to a defined policy, with alerts to affected parties. Support manually reassigning a booking to a different centre or partner when required
Partner practice accessPartner practices access the system to manually upload available slots, pricing and capability details. Booking with these partners is handled manually
Automated partner integrationOne partner group is integrated automatically through its scheduling API; all other partners are integrated manually. Preferred locations load initially from the referral system but may be amended in the Patient and Administration portals, with the ability to override them
Appointment consolidationSupport combining multiple studies for one patient into a single visit where clinically permitted
Patient PortalView upcoming appointments with status and complete, accurate detail; confirm or decline an offered appointment; view and print confirmations; access via single sign-on; capture patient feedback and associate it with the appointment
Administration PortalLets the Scheduling Manager manage configuration, gives visibility of appointment status, and provides reporting — the front end for all administration of the system
ReportingSupport appointment detail, partner performance and financial reporting

Non-functional requirements, as the customer wrote them

CategoryRequirement
UsabilityUse current web technologies to deliver a clean, intuitive experience that helps users complete their task without friction
UsabilityWork across a range of screen sizes, including phones and tablets, without degrading usability
ArchitecturalProvide a scalable, high-performing data platform capable of storing and querying large volumes of appointment and study data
ArchitecturalKeep the platform on currently supported technology versions, with periodic review of version suitability and planned upgrades
ArchitecturalBe configurable enough to absorb change in regulation, internal policy, clinical protocol or organisational structure without code changes
Availability and performancePerform in line with modern expectations — routine screens should feel immediate, and large reports must not take so long as to frustrate users. Precise criteria to be agreed during design
Disaster recoveryBe highly available and resilient, minimising the risk of service interruption
Configuration managementAdopt adequate configuration management and version control across all environments and documents
DeployabilityEmploy robust procedures for promoting any change into the live environment, minimising disruption to operations
ScalabilityBe designed so the solution can grow as the network expands
Data securityAll authenticated traffic must use encrypted transport, TLS 1.3 or better
Data securityHandling and transmission of patient data must comply with applicable health-data protection regulation in each region of operation

Read this list next to the Module 3 worked example and the whole exercise becomes visible. "Precise criteria to be agreed during design" is the customer declining to give you a number. "Current web technologies" is a constraint dressed as a usability requirement. And "configurable enough to absorb change in regulation, internal policy, clinical protocol or organisational structure" is a modifiability requirement that means nothing until somebody commits to how long a change may take — which is exactly what the worked example does when it holds the configuration team to one working day.


Growth assumptions you are expected to design for

These are stated separately because they drive the scalability and portability requirements rather than the functional ones:

  • Lumen expects 12% annual growth in referral volume
  • It intends to enter two further regions within three years, including one outside its current jurisdiction
  • Patient-facing use is shifting to mobile — currently ~45% of patient portal sessions, and rising
  • Partner practice numbers are expected to roughly double

Volumes and usage (Appendix B of the RFP)

Lumen attached these figures from its own operational data. Every sizing, availability and cost calculation in the module Tasks should start here; anything else you need is an assumption, and you should label it as one.

FactValue
Operating hoursReferral desk and centres 07:00–19:00 local time, ~300 operating days a year. Patient portal available around the clock
Busiest hour~12% of a day's referrals and bookings arrive in the busiest hour (Monday mornings)
Referral desk staff~350, across four regional desks
Scheduling managers and administrators~40
Lumen centre staff using the platform~900 (about five per centre)
Partner practice users~1,500 (about 2.5 per practice)
Patient portal use~60% of referred patients use it; about 3 sessions per referral (view the offer, confirm, check details); sessions last ~4 minutes
Live appointment and study records~6.5 million (18 months kept online; older records archived)
Notifying stage changesEach study passes through about 6 stage changes that notify the patient, by email and SMS
Referral management systemPublishes a change extract every 15 minutes; it has no event or webhook interface
Automated partner groupHandles ~15% of partner bookings through its scheduling API
Cost of manual handlingA referral handled by the desk by phone and email costs ~$9 of staff time; Lumen's target for an automated booking is ~$2
Outage toleranceLumen's finance director will accept up to ~$100,000 a year in outage-related cost (manual fallback, overtime, missed slots)
TimelineFirst release live within 12 months of contract signature; a phased roll-out by region is acceptable
EvaluationSolution fit 35%, delivery approach 20%, service capability 20%, total cost over five years 25%. The budget is not disclosed

Two things the RFP does not say, and that you should raise as clarification questions rather than guess silently:

  • How Lumen's own 180 centres publish their availability. The search requirement names only partner availability and manually uploaded slots.
  • How the Billed stage reaches Lumen's finance system. The workflow ends there, but no finance integration is listed.