Proposed Healthcare Building Brain Pilot

A lightweight MovementAI pilot forProfessional Health Care of Pinellas.

PHC operates a multi-location outpatient healthcare platform across Tampa Bay. Because the owner relationship may align the healthcare practice, the facility, and the operating data, one PHC clinic is an unusually strong test environment for proving how a Building Brain can surface full building movement friction — patients, staff, rooms, parking, deliveries, vendors, cleaning, maintenance, access points, and building systems — without touching clinical care decisions.

Whole-building view
Seven-location context
No PHI used

Executive Proposal

Pilot a PHC Building Brain as a measured, low-risk healthcare operations study.

Professional Health Care of Pinellas is a strong candidate for MovementAI because its clinics operate like living healthcare logistics systems. Patients arrive in waves, front desks verify and route demand, rooms turn over, providers move through compressed schedules, deliveries and vendors enter the building, cleaning and maintenance work around care activity, parking and curb flow affect arrival timing, elevators or shared access points can create pinch points, and building systems shape comfort, readiness, and patient experience.

The recommended first step is not a heavy technology installation or a broad AI deployment. It is a focused operating study inside one PHC facility using PHC-approved, non-clinical signals to understand where friction begins, how it spreads, and which practical actions can reduce it. This creates a safe bridge between the healthcare white paper thesis — small property issues become owner problems fast — and the USPS pilot model: start lightweight, learn the facility, prove value, then define the full Building Brain roadmap.

The strategic advantage is the owner/operator relationship. When the business and building decision-maker are aligned, MovementAI can support the care environment and the property at the same time: smoother patient and staff flow, cleaner delivery and vendor coordination, better room and equipment readiness, stronger building-service visibility, smarter capital planning, and a repeatable model for future PHC locations — without entering clinical decision-making.

Why PHC Is a Strong Fit

PHC is not just a healthcare practice. It is a living operating network.

The pilot opportunity is strongest because PHC combines patient-facing healthcare operations, multiple facilities, likely owner/operator alignment, and visible daily friction into one practical test environment.

Healthcare operations

Primary care, internal medicine, family medicine, behavioral health, telehealth, hospitalists, and long-term care coordination create recurring daily movement patterns.

Owner/operator alignment

When the same relationship can influence care operations and facility priorities, the pilot can move faster than a landlord-only or tenant-only deployment.

Patient and staff flow

Appointments, arrivals, check-in, room turnover, provider timing, front-desk pressure, and care-team movement are exactly the kind of signals MovementAI is designed to connect.

Low-friction first step

The opening pilot can study one facility with approved, non-clinical operating data before any deeper integration or sensor recommendation is proposed.

Pilot Positioning

A safe, practical first step for full clinic movement intelligence.

MovementAI can begin as a focused building-operations study before PHC considers any deeper facility integration.

Proposed Framing

Why PHC

PHC’s outpatient clinics bring together patient appointments, care-team timing, room turnover, telehealth, front-desk operations, parking, deliveries, vendors, cleaning, maintenance, access points, equipment readiness, and multi-location ownership considerations. That makes one PHC clinic a strong, practical setting for a focused Building Brain pilot.

Initial scope

The proposed first step is a limited 30-day building-intelligence study at one facility. PHC selects the location and the first movement question, then MovementAI maps the approved non-clinical signals around that question.

Trust boundary

The pilot is designed around healthcare trust from the beginning. It does not use clinical records, evaluate care decisions, score patients, or rank staff. It studies how the full facility moves and where movement friction creates preventable pressure.

End product

PHC receives a concise owner/operator evidence brief showing what building movement friction was found, which signals mattered, what practical actions were recommended, what improved, and whether a live Building Brain should be expanded.

Pilot principles

• Begin with one PHC facility and one clearly defined building movement question.

• Use only PHC-approved, non-clinical operating and facility signals.

• Study people, rooms, deliveries, vendors, cleaning, maintenance, access, parking, equipment, and building systems together.

• Deliver a practical owner/operator evidence brief before any deeper integration is considered.

Built-in protections

No PHI, diagnosis, treatment data, or clinical notes

No patient scoring or medical decision-making

No individual staff productivity ranking

No replacement of PHC’s existing clinical, billing, or scheduling systems

No expansion beyond the written pilot scope without PHC approval

No technology installation until the first operating evidence supports it

Full Building Movement Layer

MovementAI studies the whole clinic ecosystem, not just people.

A PHC facility is a daily operating network where people, supplies, equipment, rooms, vendors, vehicles, building systems, and service work all move through the same limited space.

People flow

Patients, visitors, providers, care teams, front-desk activity, telehealth overlap, and handoffs.

Arrival and access

Parking, curb activity, patient drop-offs, lobby entry, wayfinding, and accessibility pinch points.

Deliveries and vendors

Medical supply deliveries, lab pickups, pharmacy/vendor visits, service windows, loading activity, and corridor conflicts.

Building services

Cleaning, maintenance, waste handling, equipment checks, room resets, after-hours work, and service interruptions.

Vertical and internal movement

Elevators where present, stairs, hallways, shared corridors, waiting areas, exam-room paths, and back-of-house movement.

Environment and infrastructure

HVAC comfort, temperature complaints, restroom availability, lighting, access doors, safety conditions, and facility readiness.

Why Connected Signals Matter

The insight comes from seeing how building movements affect each other.

Most clinic friction is not caused by one event. It forms when several normal activities collide at the wrong time. MovementAI connects those activities so PHC can prevent repeat pressure instead of only reacting to it.

From daily activity to early prevention.

Connect signals

MovementAI links approved non-clinical signals that are usually viewed separately: appointments, arrivals, rooms, parking, vendors, deliveries, cleaning, maintenance, equipment, access points, and building-system notes.

Detect patterns

Once those signals are connected, the system can see repeated relationships — for example, a vendor window plus a patient wave plus a room reset can create a hallway delay before leadership sees the full cause.

Surface early warnings

The value is not just reporting what happened. MovementAI identifies when familiar combinations are forming again, so PHC can act before friction becomes wait time, staff pressure, missed readiness, or patient dissatisfaction.

Prevent repeat issues

Each action creates evidence: what signal appeared, what was recommended, what PHC changed, and whether the problem reduced. That turns daily movement into a prevention playbook.

Examples PHC can prevent.

Arrival delays

Parking, curb pressure, lobby traffic, and appointment waves can show when patients may arrive late or stack up before check-in.

Room slowdowns

Room turnover, cleaning, equipment readiness, provider blocks, and supply movement can show which rooms are likely to fall behind.

Service conflicts

Deliveries, lab pickups, vendor access, maintenance, and hallway movement can reveal conflicts before they interrupt clinic flow.

Facility issues

HVAC comfort, elevator/access constraints, restroom availability, lighting, doors, and maintenance notes can expose building problems before they become complaints.

Owner Value and Deliverable

PHC receives evidence it can act on, not another abstract technology pitch.

The pilot should make the business case clear: what signals PHC already has, what those signals reveal, what can be prevented, and what the owner should do next.

Likely approved signal sources

• Scheduling timestamps and appointment density

• Check-in, check-out, and room-status timing

• Maintenance notes, work orders, and facility complaints

• Cleaning schedules, room reset windows, and waste-service activity

• Vendor calendars, delivery records, lab pickups, and supply movement

• Parking, curb, lobby, elevator, corridor, and access observations

• HVAC comfort, restroom, lighting, door, and equipment-readiness notes

• Weather, traffic, local events, and peak-day context

What the owner gains

• Fewer avoidable patient-flow disruptions and complaints

• Better delivery, vendor, cleaning, and maintenance scheduling

• Earlier visibility into facility issues before they affect operations

• Clearer evidence for where capital improvements are actually needed

• Cleaner multi-location comparison across PHC clinics

• A prevention playbook PHC can reuse instead of one-time troubleshooting

Day-in-the-life example

A preventable issue before it becomes a complaint.

A morning appointment wave overlaps with a lab pickup, a supply delivery, room cleaning, and a curb drop-off surge. Separately, each event looks normal. Connected together, they explain why the lobby backs up, Room 4 turns late, staff get pulled into workarounds, and patients feel the delay. MovementAI turns that pattern into an early warning so PHC can move the delivery window, protect the hallway, prepare the room earlier, and prevent the same pressure from repeating.

What the 30-day brief includes

• Signal map showing which approved data points were connected

• Friction timeline showing when pressure formed and what contributed to it

• Preventable-issue list ranked by operational and owner impact

• Recommended scheduling, vendor, facility, and room-readiness changes

• Facility investment flags for recurring building or access problems

• Expansion recommendation for whether a live Building Brain is justified

Interactive Pilot Explorer

Choose the first operating question before choosing technology.

The strongest pilot starts with one visible building movement question, then proves which signals, actions, and evidence matter.

Selected Pilot Lens

Patient arrival waves

When do scheduled arrivals exceed the clinic’s ability to check in, room, and route patients smoothly?

Signals

• Appointment density

• Arrival timestamps

• Check-in duration

• Front-desk queue windows

Flow Cards

• Pre-stage intake coverage

• Separate appointment waves

• Open overflow check-in support

Evidence

Arrival-to-room timing, patient wait exposure, front-desk pressure, and improved flow after action.

Pilot Data Approach

Use the building and operating signals PHC already creates.

The first pilot should not require new medical systems, clinical decision support, or protected health information. It should begin with non-clinical signals that reveal how people, rooms, equipment, deliveries, vendors, access points, and building services move throughout the day.

No diagnosis data
No clinical notes
No patient scoring
No staff surveillance

Approved Non-Clinical Signals

A practical signal map for one clinic.

• Appointment volume by hour
• Scheduled versus actual arrival timing
• Check-in and check-out timestamps
• Room turnover and room readiness
• Provider schedule compression
• Front-desk queue pressure
• Telehealth versus in-person appointment load
• Parking, curb, lobby, elevator, hallway, and access observations
• Medical supply deliveries, lab pickups, and vendor service windows
• Cleaning, waste, maintenance, and room reset activity
• Equipment readiness, device availability, and service interruption notes
• HVAC comfort, restroom availability, lighting, doors, weather, traffic, and local event pressure

Practical Visual Output

The pilot should show a simple operating board PHC leaders can actually use.

This preview translates the Building Brain concept into daily clinic visibility across people, rooms, access, deliveries, vendors, equipment, and building services.

PHC Clinic Command Preview

Morning Readiness Board

Non-clinical operating signals only

84

Building readiness

Strong, but intake and service pressure rising

12 min

Arrival risk

Projected front-desk and curb compression

3 rooms

Turnover watch

Rooms 2, 4, and 6 need attention

10:15 AM

Service overlap

Vendor delivery plus patient wave

Pressure Timeline

7:30 Open

8:15 Arrival

9:40 Peak

10:15 Delivery

12:00 Reset

Live Flow Cards

High Priority

Protect intake, curb, and lobby flow from 9:25–10:10

Expected to reduce arrival compression before room delay forms.

Medium Priority

Prepare Room 4 and confirm equipment readiness before the next provider block

Turnover timing and equipment availability could affect two appointments if unchanged.

Medium Priority

Delay non-urgent vendor delivery until after 11:00

Service corridor overlap could add lobby, hallway, and staff friction.

Daily proof: the board records what pressure formed, what action was recommended, whether PHC acted, and what changed afterward.

What PHC Receives

The pilot should produce evidence-ready intelligence, not a technical science project.

The goal is to convert ordinary clinic activity into visible, usable evidence that helps PHC improve experience, reduce pressure, and plan the building intelligently.

Morning Clinic Readiness Brief

A plain-language view of likely appointment pressure, room-readiness risk, front-desk load, staffing constraints, and facility friction before the day becomes reactive.

Patient Flow Friction Map

A visual map showing where arrivals, check-in, provider timing, rooms, telehealth blocks, staff handoffs, and facility nodes are creating avoidable delay.

Flow Cards

Ranked, practical recommendations such as adjusting intake coverage, preparing rooms earlier, separating appointment waves, or changing vendor timing.

Owner Evidence Report

A record of what happened, which signals mattered, what action was recommended, what improved, and which capital or operational upgrades deserve attention.

Success Criteria

The pilot needs a scorecard before it starts.

A comprehensive proposal should define how PHC will know the pilot worked. The right measures are operational, non-clinical, and evidence-ready.

Recommended pilot target

Produce at least three validated Flow cards, one friction map, one owner evidence brief, and one practical scale recommendation within the first 30 days.

Measurement Framework

What should be measured.

Patient flow

Arrival-to-room time, check-in compression windows, avoidable waiting exposure

Room readiness

Room turnover variance, provider idle time, same-day schedule compression

Staff pressure

Peak-window coverage mismatch, interruption load, handoff timing risk

Facility friction

Parking, curb, vendor, cleaning, maintenance, and lobby events affecting clinic rhythm

Action quality

Number of Flow cards issued, accepted, ignored, or converted into operating changes

Owner value

Capital-planning signals, repeatable improvements, and expansion readiness across locations

Pilot Roadmap

Start with one facility. Learn the clinic. Prove value fast.

1

Select one PHC clinic

Choose the facility with the clearest operating question: patient arrival waves, room turnover, staffing pressure, lobby congestion, parking friction, or opening-day readiness.

2

Gather approved operating context

Review non-clinical schedules, timestamps, staffing patterns, facility notes, vendor timing, room flow, and observable friction already available to PHC.

3

Build the first signal map

Connect daily activity into a movement-friction model showing where small timing issues spread through rooms, people, providers, and shared spaces.

4

Run action-card review

Generate practical recommendations and compare them against real operating outcomes with PHC leadership and the clinic team.

5

Deliver the Building Brain brief

Summarize findings, early wins, missing signals, recommended integrations, and the operational roadmap for a live facility intelligence layer.

6

Decide scale path

If the pilot proves value, extend to deeper data feeds, a live dashboard, zone displays, or additional PHC locations.

Candidate Facility Network

PHC’s seven-location footprint makes one clinic a useful proof model for the whole platform.

The first pilot should be deliberately narrow, but the results should be structured so PHC can compare friction patterns across other clinics later.

Central St. Pete / Grand Central
West St. Pete / Five Towns
North St. Pete / MLK Street
Pinellas Park
Dade City
Seminole
Northside / 49th Street

Healthcare Guardrails

This is a building-operations pilot, not a clinical AI pilot.

The safest and strongest framing is that MovementAI reads building behavior, operating timing, and movement friction. It does not make diagnoses, recommend treatment, replace clinicians, or evaluate patient care decisions.

The pilot protects trust by staying focused on flow, readiness, friction, and owner/operator evidence.

Written Boundaries

Recommended pilot conditions.

Written scope before data review begins
PHC-approved access only
No PHI, diagnosis, treatment, clinical notes, or patient scoring
No individual employee productivity ranking
No replacement of existing EHR, scheduling, billing, or clinical systems
Findings reviewed with PHC leadership before any expansion
Clear separation between operating intelligence and medical decision-making
Optional deeper integrations only after the first evidence brief

Pilot Readiness

A focused path from first review to informed expansion.

This proposal is structured so PHC can evaluate MovementAI as full building-operations intelligence through a limited, practical, healthcare-safe pilot before making a larger technology decision.

Clear first step

Begin with one facility, one operating question, and one 30-day non-clinical signal review.

Practical decision path

PHC receives a defined evidence brief before deciding whether to expand, integrate, or install anything deeper.

Useful daily visuals

The pilot output is designed to show readiness, pressure, Flow cards, and evidence in language clinic leadership can use.

Healthcare-safe scope

The pilot stays outside PHI, diagnosis, treatment, patient scoring, staff surveillance, and clinical decision-making.

Owner/operator value

The findings support patient experience, staff rhythm, deliveries, vendor coordination, facility services, capital planning, and multi-location learning.

Repeatable model

If one PHC clinic proves value, the same signal-review method can be adapted to other PHC locations.

Recommendation

Ask PHC for one facility, 30 days of approved non-clinical signals, and one owner/operator review meeting.

The cleanest ask is simple: select one PHC facility and one visible building movement question — patient arrivals, room turnover, parking and curb flow, delivery timing, vendor access, cleaning windows, elevator or corridor pinch points, maintenance activity, equipment readiness, or telehealth/in-person overlap — then let MovementAI translate that daily activity into a signal map and owner evidence brief.

The review gives PHC a practical decision package: what happened, why it happened, what could have been prevented, what operating changes are recommended, and whether a live Building Brain should be installed more deeply.

Recommended pilot: PHC Healthcare Building Brain Pilot — one facility, approved existing signals, non-clinical building intelligence, evidence-ready prevention evidence.

Owner pilot

Turn friction into a clear decision.

Start with your messiest movement problem. We'll map the signals, deploy intervention cards, and capture the proof.

Build the memory

Start with one asset, workflow, or zone and define the rules the Building Brain needs.

Flow the decision

Turn one live movement problem into a clear intervention card or dashboard event.

Sync the proof

Create a simple record of what happened, what action was taken, and what improved.

Building Brain Delivery

Deliver the brain as Flow cards, a central dashboard, or both.

Action cards

Route the brain’s next move directly to the people or teams who need to act.

Central dashboard

Collect every movement decision and evidence thread in one owner/operator view.