Drawing the layer000

Healthcare systems studio

Making systems make sense.

We connect the software and data behind hospitals and clinics, so records, labs, imaging and administration can finally work as one.

See how we work
Figure 1: six systems become one layerAn isometric drawing of six slabs labelled Records, Labs, Imaging, Admin, Scheduling, Billing, assembled into one connected layer.
Fig. 01Assembled view

RecordsLabsImagingAdminSchedulingBillingOne layer

01ApproachFrom fragmented to connected

Good systems should talk to each other.

Most hospitals already own the right pieces. The work is in the joins: shared formats, clear ownership, interfaces that survive the next upgrade.

02ConceptsExplorations, not case studies

A few ideas in motion.

  1. SourcesShared modelApplication
    Concept 01Interoperability

    One pathway for patient data

    An exploration of how records from several departments could arrive in one place, in one shape.

    • Integration
    • Data model
    View concept
    Sheet
    01 / 03
    Status
    Exploration
  2. 01 Ward02 Transport03 Analyzer04 Clinician
    Concept 02Clinical workflow

    Following a lab result

    A study of every hand-off between a sample leaving the ward and a result reaching the clinician.

    • Workflow
    • Automation
    View concept
    Sheet
    02 / 03
    Status
    Exploration
  3. Shared busRecordsLabImagingBookingBillingPharmacy (next)
    Concept 03Architecture

    A shared bus for small clinics

    A sketch of a lightweight integration backbone that smaller practices could adopt one system at a time.

    • Architecture
    • Platforms
    View concept
    Sheet
    03 / 03
    Status
    Exploration
  4. More in progress

    New concepts are drawn as we learn. Real projects will live here.

    See what we do
03ServicesFrom mapping to deployment

Where we come in.

Three ways in, one direction: fewer disconnected systems, and data that is ready to be used well.

  1. 01Integration

    Connect the pieces.

    We map how information moves between clinical and administrative systems, then design the interfaces that let it move cleanly.

    • System mapping
    • Interfaces
    • Data exchange
    System ASystem BInterface
    Sheet
    01 / 03
    Scale
    1 : 1
  2. 02Platforms

    Give data direction.

    We shape shared data models and platforms so every team works from the same source, with clear ownership.

    • Data platforms
    • Data flows
    • Modernization
    AppsPlatformSources
    Sheet
    02 / 03
    Scale
    1 : 1
  3. 03Applied AI

    Make room for intelligence.

    Once data is connected and governed, we build careful automation and AI on top of it, with people in the loop.

    • Applied AI
    • Workflows
    • Prototypes
    Governed dataModel, with people in the loop
    Sheet
    03 / 03
    Scale
    1 : 1
04PerspectiveFig. 02, a hospital in section

Designing what's possible.

A hospital is a building full of systems that rarely meet. We design the layer that runs through all of them.

Figure 2: a section through a hospital with one connecting layer running through every floorInfrastructureReceptionImagingLabPharmacyEmergencyWardsClinicRecordsOutpatientsAdminSchedulingBillingTheatreStaffOne layer, every floor
05StudioSmall team, open drawings

Humans behind the systems.

A small founding team of engineers and designers who like hard, tangled problems and the quiet satisfaction of untangling them.

  • Portrait pending
    Founder 01

    [Founder name]

    [Role, focus area]

  • Portrait pending
    Founder 02

    [Founder name]

    [Role, focus area]

  • Portrait pending
    Founder 03

    [Founder name]

    [Role, focus area]

06ContactAn open invitation

Untangling a system, or planning the next one?

Let's make something click.

What is it about?

Please leave out patient data or any other health information.

Figure 3: from one layer, new things rise: Apps, Analytics, Automation, AI01 Apps02 Analytics03 Automation04 AIThe connected layer