Reads the released artwork and IFU and lists each symbol and statement with its place.
- Never reads unreleased artwork
- Never decides when the label is silent
GUDID, EUDAMED and the ERP item master read against the released label artwork, so a wrong value is corrected for its whole family and signed by a steward who opened the sample.
Follow one MR Unsafe symbol from line-up to signature ↓One device fact lives in the product lifecycle system, the ERP item master, the labeling system, GUDID, EUDAMED, China's UDI database and the instructions for use. When a label template changes, each team updates its own system from its own copy, and the field that feeds the GUDID load keeps its old default.
Submission validators check that a record is complete and well formed. They do not open the label. A mismatch turns up by accident, in a hospital's item master or a data pool rejection, and gets fixed one identifier at a time while the rest of the family carries the same error. Past the grace period, a fix done the wrong way creates a device identifier that should not exist.
Built forUDI data stewardsMaster data analystsLabeling specialistsRegulatory affairs teams
The same device fact sits in six systems, and each team updates its own system from its own copy.
Compared by hand today
Built-in controls
Database records an auditor can trace to the released label, with a signed reason for each change.
Friday's overnight sweep read 100,240 active identifiers and found 4,812 mismatches on 2,906 of them. The master data analyst starts on Tuesday with a bidirectional ablation catheter.
demoThe manufacturer, its catheters, the people, the identifiers and the counts are sample data.
The released artwork sits across the top as seven anchors: sterile EO, do not re-use, not made with natural rubber latex, MR Unsafe, use-by date, quantity one, keep dry and away from sunlight. Under each anchor sits a row per system, from product lifecycle to the IFU. Each cell reads not read yet until the agents run.
Six agents run in order and compare 60 attributes. GUDID holds that the labeling does not contain MRI safety information. The ERP field that feeds the GUDID load reads NOT LABELED. EUDAMED's storage text says keep dry and leaves out keep away from sunlight. The other cells agree with the label, each with its source.
He opens the GUDID cell. The record, the field, the value held and what the label says sit together: MR Unsafe, at position 4 of the symbol row, added by template rev C. The agent's reading says the record should read MR Unsafe, with a confidence of 0.97 labeled as sample data. Nothing changes until people agree.
Because the label did not change the device, this is an error correction and no new identifier. Past its 7-day grace period, the GUDID record is opened for edits by the coordinator for 5 calendar days. An ERP change request stops the next load from overwriting the fix. EUDAMED storage is updated in place. China's database maps no MR field, so nothing is drafted there.
The sibling finder followed template LT-EP-04 rev C to five electrophysiology catheter families, all with the same two gaps. For a batch of 150 identifiers or fewer, the rule in force draws 5 records, and it leaves out the one the analyst already read. Approve stays locked until she opens the sample. No timer opens it.
A sampled decapolar catheter shows its identifier, its label template, what GUDID and the ERP hold now and what is drafted, and the released artwork with the MR Unsafe symbol at position 4. A record counts as opened after 3 seconds and her verdict: matches the label, or does not. Her opens count for her alone.
She signs as herself, with her own user ID and password. The meaning reads: approved, I opened the 5 sampled records and approve these 282 corrections for submission. The step bar moves on, and the screen says the labeling specialist must open each record herself before she can sign. Five green lines show how long each record was open.
Her opens are logged under her own session. She signs checked against the approved label, with the reason that the sample matches the released artwork. Two people have now signed the batch for two different things, each with a session code. The next step names the regulatory affairs specialist, and the ERP part waits for the analyst to post.
Approved and checked, the batch shows one button on her screen. Once she submits, the submission tracker reads back each acknowledgment and the published value, and reopens any record that did not land. The EUDAMED storage fix travels in its own batch, and the analyst posts the 141 ERP changes from his queue.
The change rule checker applies these before anything is drafted. Where a new identifier is needed, nothing is drafted and a person owns the route.
| What happened | GUDID | EUDAMED |
|---|---|---|
| The label changed the version, model or package quantity | New device identifier (21 CFR 830.50) | New UDI-DI |
| The label did not change; the database holds a wrong value | Error correction: the record is reopened for 5 calendar days | Correct the record in place |
| MRI safety status wrong, label unchanged | Error correction, record reopened | No EUDAMED element |
| Storage and handling, GMDN or EMDN code, contact, instructions address | Edit in the grace period, or error correction after it | Update in place |
| China's record wrong, label unchanged | None | China's own correction procedure, through the registration agent |
demoSample data, from the working solution. A label change to single use, sterile packaging, latex or quantity per package needs a new identifier, so those findings go to a person with no draft.
The sibling finder follows the cause, not the product name.
| Irrigated ablation catheters | 22 |
| Steerable decapolar diagnostic catheters | 36 |
| Fixed-curve quadripolar diagnostic catheters | 44 |
| Circular mapping catheters | 24 |
| Non-irrigated ablation catheters | 15 |
| Identifiers in batch B-14 | 141 |
| Corrections: one GUDID edit and one ERP change for each identifierOpen mismatches go from 4,405 to 4,123 once all 282 are read back. | 282 |
demoSample data, from the working solution.
What the analyst, the steward and regulatory affairs open between line-ups.
demoSample data, from the working solution.
The approved label is the source of truth, and people decide what goes out.
Reads the released artwork and IFU and lists each symbol and statement with its place.
Pulls the identifier's record from each system and database.
Maps each system's field and value to the label's meaning and compares them.
Decides whether a change is an edit or needs a new identifier, from the loaded rules.
Writes each correction in the target database's own field and wording, and the ERP request.
Follows a cause, such as a template revision or an ERP default, to each identifier sharing it.
Reads acknowledgments and the published record after a person submits.
The agents draft from the label. These calls belong to a person.
It checks that GUDID, EUDAMED, China's UDI database and the ERP item master say what the approved label says. This GUDID reconciliation reads the released artwork and IFU, lines up each system's value under each symbol, and drafts corrections for people to approve and submit.
No. The steward approves after opening a sample, the labeling specialist checks it, and regulatory affairs submits. The submission tracker then reads back the acknowledgment and the published value.
The change rule checker marks it and nothing is drafted. The finding goes to regulatory affairs and labeling, who own the new identifier.
The rule in force draws a sample by batch size and leaves out records already examined. Approval stays locked until each sampled record is opened and given a verdict, and the largest batches need a second approval from the director.
Yes. Both issuing agencies' identifiers sit in the inventory and are read against their labels, and search matches GTINs, HIBCC codes, catalog numbers and Basic UDI-DIs.
It feeds the GUDID load. A default left in an ERP field overwrites a corrected GUDID value on the next load, so each GUDID fix comes with an ERP change request.
Every closed CAPA proved with its own sums, and the same cause found where the fix never went.
1-min demoNonconformance (NCMR) Investigation and MRB DispositionEvery MRB call made on the records, not on memory, with each seat's signature.
1-min demoFDA 483 and Warning Letter ResponseEvery promise to FDA has an owner, a date and its proof.
1-min demoWe will line up what each database says under its symbols and show which values drifted.