WorkflowManufacturing & Sterilization

Patient-Specific Implant Case File Verification

Patient-specific implant case file verification that compares the plate as built with the revision the surgeon signed, holds a mismatch at once, and leaves the design call to her.

Follow one plate from a passed inspection to its release ↓
Watch with transcript →
The problem

An inspection that passes against a drawing the surgeon never approved

A patient-specific case lives in several systems. The surgeon's approval sits in the case portal, the revisions in product lifecycle management, and the build record, inspection report, sterilization record and label proof in the quality system and the ERP. Nobody joins them back to the one revision the surgeon signed.

So the inspection report says pass because it measured the part against the drawing manufacturing was given. If that drawing is a later revision, released without engineering review, each number passes and the case is still wrong. The case ships days before surgery, and a remake takes days.

Built forPatient-specific design engineersQA release specialistsCase coordinatorsSurgeons

The Problem Today

Inspection measures the part against the drawing it was given, not the revision the surgeon signed.

Joined by hand today

  • Approval
  • Revisions
  • Inspection
  • Label
  • Latest is not approvedA later revision can reach the build with no review
  • Days before surgeryA wrong plate found late means a remake after the date

The Solution

  1. Read the whole case fileOrder, imaging, plan, revisions, build, inspection, sterilization, label
  2. Compare each featureEach hole and bend as built against the signed plan
  3. Hold at onceA mismatch opens a nonconformance and goes to the design engineer
  4. People decideThe engineer proposes, QA agrees, the surgeon decides, QA releases

Built-in controls

  • The baseline is the signed revision, never the latest
  • Only the surgeon approves a design for her patient
  • The full patient identifier stays masked

What You Get

Each plate leaves matching the revision the surgeon signed, or it waits for her decision.

3,750 h
of case file checking saved yearly at a big maker our estimate
  • Every hole and bend checkedAgainst the approval record, with sample tolerances
  • Held before it shipsA design change that skipped review becomes a nonconformance
  • Label checked tooDesign version, use-by and side against the case
One case, two days before shipping

A patient-specific implant held at 08:54 and released at 11:58

A right mandible reconstruction plate: three segments, two bends, eleven screw holes. Its last records closed at 08:40. It ships in two days.

demoThe case, its plate, the surgeon, her hospital, the staff and each measurement shown are sample data.

  1. 0108:52

    All records have closed, and no one has looked at a number yet

    Design engineer

    On the schematic of the patient's mandible sits the plan the surgeon signed, holes outlined and not yet read. Nothing is checked against the latest revision. The panel says what will happen: seven agents read the case file, lock the revision the surgeon signed, and compare each screw hole and bend with it.

  2. 0208:53

    13 records read, and three of them used a revision nobody approved

    Design engineer

    The case file reader indexes the order, imaging, plan, three revisions, the approval, build package, build record, inspection, sterilization, label and packing list. Next, the revision lock finds the surgeon signed rev 2. The build package, the inspection drawing and the label all used rev 3, which has no engineering approval.

  3. 0308:54

    Bend B2 is 6.1° off the signed plan, so four holes sit as far as 3.39 mm away

    Design engineer

    Against rev 2, holes H8 to H11 are 0.83 to 3.39 mm from the plan, outside the sample tolerance of 0.30 mm. The other seven holes are within 0.04 mm and B1 within 0.2°. 8 of 13 features pass. The case holder placed the hold and opened a nonconformance at 08:54.

  4. 0408:55

    The inspection report passed, measured against the rev 3 drawing

    Design engineer

    She opens the coordinate measuring report herself. All values are there, and each passes against the drawing it was given: B2 measured at 24.1°, within 0.1° of rev 3. That is why nothing upstream raised a flag. A check that passes against the wrong revision does not count here.

  5. 0508:56

    Rev 3 moved B2 from 18.0° to 24.0°, as an internal draft

    Design engineer

    The revision itself says why: segment 3 follows the planned bone segment more closely, and the last four holes move with it. It was never reviewed by engineering and never sent to the surgeon, yet the build package rule took the latest revision. She did not author it, so she can review it inside the nonconformance.

  6. 0609:20

    Her proposal: use as is, only if the surgeon approves rev 3

    Design engineer

    Rev 3 sits inside the design envelope, which she has opened too. Her signature states that she reviewed rev 3 as a design change within the nonconformance, did not author it, and proposes a disposition QA must agree. She types her own reason. The other choice was a remake to rev 2, after the surgery date.

  7. 0709:22

    QA release opens the nonconformance before agreeing

    QA release specialist

    As the second person on the disposition, she opens the inspection report and the nonconformance record, which notes the extent check: none of the other 25 case files read this week was built from a revision other than the signed one. She agrees in her own words at 09:41, so rev 3 goes to the surgeon.

  8. 0811:32

    The surgeon reads rev 3 on her patient's model and approves it

    Surgeon

    In her own guest view she sees only her case: rev 2 dashed and rev 3 solid on the model, with the bend and segment 3 moved. She opens rev 3 in full, picks her reason and signs. Declining would have sent the case to a remake. No agent offers her a recommendation.

  9. 0911:58

    Released at 11:58, after a fresh read found 13 of 13 within tolerance

    QA release specialist

    The agents re-read against rev 3 at 11:34, and the label's design version now matches. She opens the re-read results, the surgeon's decision and the carton label proof, each for three seconds, then releases the case with her own words. Released this week moves to 10 of 31. The nonconformance closes as use as is.

One bend, measured against two revisions

The same plate, compared with what the surgeon signed and with what manufacturing was given.

FeatureAgainst rev 2, signedAgainst rev 3, built
Bend B26.1° off0.1° off
Holes H8 to H110.83 to 3.39 mm off0.07 mm or less
Other seven holes0.04 mm or less0.04 mm or less
Bend B10.2° off0.2° off
Features within sample tolerance8 of 1313 of 13

demoSample data, from the working solution. The baseline never moves to the latest revision on its own. Rev 3 became the baseline only after the surgeon signed it.

Around the release

Revision lock, label check and the week's custom implant cases

What QA release and the case coordinator read beside the hero case.

The fresh readRead again after the surgeon signed rev 3: 13 of 13 within the sample tolerances, side, size and label in agreement, ready for QA release.
Revision lockEach revision with who approved it, and which revision each downstream record used. A part built from an unapproved revision is a nonconformance.
Label checkThe carton label against the five labeling items and the patient-matched items. The patient identifier is masked for everyone but the coordinator.
Case file checklist16 of 17 checks agree across the case's records, each opening its source, from order and imaging to the cleaning record.
This week's cases31 cases due to ship this week, 10 released, 13 checked and waiting, 3 held, each with its clock and owner.
Audit trailEach entry names a person, an agent or the system: openings, the surgeon's approval, the re-read and the release with its meaning.

demoSample data, from the working solution.

Four signatures on one plate, and no one reviews their own work

The author of a revision cannot review it, and the proposer cannot agree.

Design engineer
Sees
The revision built, the inspection report and the design envelope
Signs
Proposes the disposition as a non-author
QA release specialist
Sees
The inspection report, the nonconformance and the release records
Signs
Agrees the disposition and releases the case
Surgeon
Sees
Her own case, both revisions on her patient's model
Signs
Approves or declines the design
Case coordinator
Sees
The label and the masked patient identifier
Signs
Reveals the identifier with a logged reason
Who reads the case file

Seven agents compare and hold, and none approves a design

They read records and measure. People decide the plate.

Case file reader

Reads a case's records and indexes revisions, dates, side and serials.

  • Never sees the full patient identifier
Revision lock

Finds the revision the surgeon signed and which revision each record used.

  • Never treats latest as approved
As-built comparer

Compares each hole and bend from the inspection report with the signed plan.

  • Never judges clinical acceptability
  • Never edits a design
Side and size checker

Checks side on the order, design, part mark, label and packing list.

  • Never corrects a side; a person checks the part
Envelope checker

Checks each design parameter against the device master record's envelope.

  • Never approves a design
Label checker

Checks the label items and sets use-by from the earlier of imaging and sterile dates.

  • Never prints or changes a label
Case holder

Holds at once, opens the nonconformance and runs the extent check.

  • Never releases, lifts a hold or contacts a hospital

What QA release asks about patient-specific implant case files

What is patient-specific implant case file verification?

It checks a patient-specific implant before it ships: every record of the case is read, the revision the surgeon signed is locked as the baseline, and each screw hole and bend as built is compared with it. A mismatch is held at once and goes to a design engineer.

Why not compare against the latest revision?

Because the latest revision may never have been reviewed or sent to the surgeon. An inspection can pass against that drawing while the plate still differs from the approved plan.

Does it judge whether a design is right for the patient?

No. It compares measured values arithmetically against sample tolerances. Only the surgeon approves a design for her patient, and clinical questions go to her.

Does it replace our virtual surgical planning or case portal?

No. It reads the case portal, product lifecycle management, the quality system and the ERP, and joins them back to the signed revision. Planning and approval stay where they are.

What happens when a part was built from an unapproved revision?

A nonconformance opens. A design engineer who did not author the revision reviews it and proposes a disposition, QA release agrees or sends it back, and the surgeon decides if the design changed.

Who sees the patient's identity?

Nobody by default. The identifier is masked everywhere, and only the case coordinator may reveal it, with a reason that is logged.

What if a surgeon's words describe a problem with a device or a patient?

Those words are not accepted in the reason box and are not read by the agents. The surgeon is shown the complaint handling contact instead.

Pick a shipped case
and its signed approval.

We will compare each feature with the revision the surgeon signed and show you anything built from another.