Bought by the health system. Used first by the people who build.

Four seats inside the system carry a piece of the AI question by hand today. Vendors are the fifth, on their own page.

Builders

TodayFind out which provider is allowed, get credentials, handle PHI correctly, wait for approval, then integrate against provider-specific APIs. The desired experience is one sentence: give me the endpoint and tell me what models I can call.
  • One key to every approved modelThe provider agreements are already in place when you start.
    The provider registry
  • A sandbox today, a route this weekRequest a route from the console; Privacy approves it with the validator's findings in front of them.
    The prototype
  • A budget you can seeSpend against ceiling by application and by route, and denials with reasons.
    The builder view
  • A comparison when a version changesOld and new on your own samples. You propose; Privacy approves.
    The upgrade

The CISO

TodayEach AI vendor or application adds another data path, credential set, provider relationship, and control surface. Every one of them is secured separately.
  • Review the shared AI path onceApplications and vendors reuse it. A model change is a policy edit.
    The backlog
  • Unregistered AI traffic is refused and loggedA key that matches no entry gets a denial and a row in the record.
    The caller registry
  • Runs in your VPCThe gateway, the policy, the credentials, and the records are in your account.
    Security & deployment

The privacy officer

TodayDeciding, again and again, whether a particular application may send particular data to a particular model, and then relying on the application team to do it correctly.
  • Identifiers replaced per route, before sendingThe record shows which identifier types were found and what was done with each.
    The record
  • A queue with the evidence attachedRoute requests arrive with the validator's findings. Approve, approve with an edit, or ask.
    Yes in a week
  • An answer for the inquirySix years of records by patient, caller, route, and date.
    The inquiry
  • Every obligation has a named ownerWhat Miso enforces and what each caller attests to, with the state overlays.
    State overlays

The CIO and the board

TodayAI is proliferating across departments with no coherent architecture. The inventory is a spreadsheet updated before board meetings, and open access for internal teams has no ceiling.
  • One set of provider agreementsNegotiated once. Every application and vendor works under them.
    The provider registry
  • Open access with a ceilingBudgets by team and by route.
    Routes
  • An inventory from trafficFor everything routed through Miso, one page answers what AI is running here.
    The board page
  • The chain for the big dealWhich agreement covers which route, before signature.
    The deal