Platform / Provider onboarding

Files stall on the reply, not the verification.

The questions that hold a file open are the ones only the provider can answer, and they are asked by email, in a packet, between shifts.

Request accessRead the verification gap →
Provider · phoneThu · 8:41 PM
Facility Portal · Provider fileSent
Waiting on the provider0 of 6 fields

Values are illustrative. The field names are the ones the record actually writes to.

Where the weeks go

Nobody is stuck on the state board.

A license check is a query. Seven unexplained months in 2016 is a conversation with somebody who is on shift.

Verification is the tractable half. Sources answer. What holds a file open is the short list only the provider knows — why the dates do not line up, which registration is current, whether a disclosure answer means what it appears to mean.

So a coordinator sends an email, then a reminder, then a packet with fourteen highlighted lines that comes back as a scan somebody re-keys into the system it should have arrived in.

Credentialing is one component of onboarding. It is the one the contract, the EHR account and the schedule all wait on.

What a reply becomes

An answer is a field, not an attachment.

Every reply lands on the file as a typed value carrying where it came from, who gave it and when.

  1. 01
    sent
    4c1f…
  2. 02
    delivered
    9a07…
  3. 03
    reply_received
    b3e2…
  4. 04
    field_answered
    17dc…
  5. 05
    profile_updated
    e58b…
  6. 06
    completed
    2f94…

The log is append-only, and each entry seals the one before it. A sequence like this one is produced rather than asserted.

Why the provider answers

The record they are filling in is their own.

A provider keeps one record on their phone and carries it, so the next facility inherits an answered file rather than an empty packet.

Chase fails for a reason nobody names: the provider is typing into somebody else’s system, for the third time this year, about facts that have not moved since the last time they typed them.

Here the answer goes to their own record first. They attest to it, section by section, on a date — and it stands behind the next appointment and the next payer application without being asked for again.

profile_field_provenance
  • field_pathemployment_gaps[2016-06 → 2017-01].explanation
  • current_valueParental leave
  • attested_atApr 3, 2026 · 8:41 PM
  • attested_viacredential_request
  • freshness_expires_atApr 3, 2027

One row. It is the reason the same answer does not have to be collected twice.

Questions we get

The response loop, plainly.

Why do credentialing files sit open?
Rarely because a source will not answer. They sit on the items only the provider can supply — an unexplained gap, a current registration, an ambiguous disclosure — asked over email while that provider is working clinical shifts, and returned as documents somebody re-keys.
How is this different from a portal the provider logs into?
A portal asks the provider to find it, recover a password, and finish a form in one sitting. Bip asks one question at a time, where they already are, and writes each answer as a named field rather than a submission somebody opens later.
Does an answer sent from a phone hold up in an audit?
Each reply is parsed into named fields and written with its source, its actor and its timestamp into an append-only, hash-chained event log. What an audit asks for is not the message. It is the field, the date, and where the value came from.
Does the provider start over at the next facility?
The record belongs to the provider, so the next facility begins from an answered file. What that facility requires of its own — local forms, privileges, its committee’s questions — stays its decision, under its own bylaws and its accreditor’s standards.

Send us the questions your files are waiting on.

We will show you what each answer looks like once it lands as a field with a source on it.

Request accessRead the market brief →