PIM for medical devices and healthcare supplies

Control medical-device and supply identifiers, variants and source documents in PIM, keeping catalogue accuracy separate from clinical suitability.

PIM for medical devices keeps the exact manufacturer model and sellable pack tied to its approved product information. Product information management (PIM) must preserve those relationships across supplier updates and storefront exports. An accurate catalogue identifies what you supply. Clinical suitability remains a separate decision for qualified healthcare professionals.

Start with the manufacturer’s identifiers and documents, then verify the item your ordering system sends to the warehouse. This approach also fits PIM for healthcare consumables, where a correct description can still hide the wrong pack quantity.

Identify the healthcare product and variant

Create separate records for a device, its accessories and its consumables. Record an explicit relationship when the manufacturer identifies compatible items. Similar names or a shared category are insufficient evidence of compatibility.

A product record needs the manufacturer’s name and model identifier alongside your retail stock keeping unit (SKU). Keep the supplier’s catalogue number separately when it differs. Record size and pack quantity as fields, with a unit for each measurement.

Resmed’s AirFit N20 frame-system page describes a replacement system containing the frame, cushion and elbow with short tube. It excludes headgear. A catalogue title that calls this a complete mask would conceal a purchasing difference. Preserve the supplied contents even when related items share the N20 name.

For Australian device identification, distinguish your stock code from official identifiers. The Therapeutic Goods Administration (TGA) explains that the Unique Device Identifier has a fixed device component, the UDI-DI. This identifies a model or version. The production component, UDI-PI, carries production information such as batch or serial details.

Keep model-level data in PIM and define its relationship to the system that holds received batches and stock. Do not turn a changing batch value into the permanent identity of every unit of that model.

The TGA’s Australian device-database guidance distinguishes an Australian Register of Therapeutic Goods (ARTG) inclusion from more detailed device records. ARTG inclusion covers a kind of medical device. Record the supporting inclusion and sponsor separately from the exact sellable model. Copying an ARTG number into PIM does not establish a model match or approve a new device.

Control technical references and revisions

Attach technical facts to the manufacturer document that supports them. Keep the document identifier and revision, its market and language, and the model numbers it covers. Preserve the source file when a replacement arrives so reviewers can compare the changes.

Use a record like the following to prevent a description from losing its conditions.

InformationRequired source relationshipPublication check
DimensionsManufacturer drawing or specification for the modelValue and unit describe the supplied item
Pack unitsManufacturer or supplier pack recordEach, box and carton quantities stay distinct
CompatibilityManufacturer’s named model relationshipThe listed accessory matches the exact model
Intended useApplicable manufacturer instructionsWording retains its conditions and limitations
Instructions for useDocument identifier, revision and covered modelsDownload opens the document approved for this item
Regulatory referenceMatched official entry and sponsor informationReference belongs to the product being described

An instructions document can cover related models while retaining different requirements for their components. Resmed’s N20 user guide distinguishes the AirFit silicone cushion from the AirTouch foam cushion. Keep model-specific instructions attached to their source instead of copying one component’s text across the family.

Record warnings with the document relationship and route changes to the authorised reviewer. A marketing description must preserve the manufacturer’s intended-use boundaries. It must not infer a broader use from a dimension, material or product category.

An empty compatibility field means the relationship is unconfirmed. Give it a distinct state from a documented incompatibility. Prevent an importer or generated answer from converting an empty field into a positive recommendation.

Verify the catalogue handover

Use a fictional healthcare-supply catalogue to test a model revision. Its manufacturer replaces accessory A10 with A11 and issues instructions revision R3. A11 measures 120 mm and is sold in a box of ten. These are invented product details for the check, not specifications for a real device.

The supplier file has two faults. It leaves the compatibility field empty and marks the pack as one item. The manufacturer’s source for this scenario identifies device D20 as compatible and confirms the box quantity.

  1. Import A11 as a proposed record. Confirm that the mapping preserves its new manufacturer identifier and does not overwrite A10’s record.
  2. Compare the proposal with the manufacturer source. Record the missing D20 relationship and the wrong pack quantity as separate exceptions.
  3. Correct both fields from that source. Attach R3 to A11 and retain A10’s existing document relationship. An authorised reviewer approves the changed record.
  4. Export the approved revision to a test storefront and the enterprise resource planning (ERP) system. Confirm that the store’s one orderable box maps to ten units in the agreed stock conversion.
  5. Inspect the product page and its document download. The page must show A11, 120 mm and the box quantity. The download must open R3, and the approved compatibility field must name D20.
  6. Refresh the catalogue used for product answers. Ask what the box contains and which manufacturer-listed model it supports. Check that the answer uses A11’s approved fields and that A10 remains unchanged.

If the store shows a single unit, inspect its unit-of-measure mapping and the exported quantity field. A successful export does not prove that the storefront interprets the unit correctly. If the download still opens the old file, inspect the asset relationship and cached document URL.

While compatibility is unresolved, suppress the compatibility assertion and route the question to a person. Keep a product update that changes supplied quantity out of publication until the pack mapping is corrected. Preserve the failed checks with the proposed revision so the integration owner can reproduce them.

Assess governance and integrations

Compare PIM access controls through the work each person can perform. A supplier can propose a new specification, while an authorised reviewer decides whether it can publish. Test whether an import account can bypass that boundary.

Akeneo’s Supplier Onboarder documentation describes mandatory review before supplier proposals affect PIM data. Its History documentation describes old and new values and the author of a change. Access to history and restore actions depends on role permissions. The documentation also says history records cannot be exported. If you need an external audit archive, establish how your operating process will retain the required evidence.

Use those documented behaviours as comparison points for the edition and modules you are considering. Ask each provider to demonstrate an unauthorised edit being rejected and an unexpected import being traced to its source.

Integration boundaryEvidence to requestResponsible owner
Supplier to PIMIdentifier matching, proposed changes and rejected-field handlingSupplier-data owner
PIM to ERPManufacturer code, retail SKU and agreed pack conversionERP integration owner
PIM to storefrontApproved fields and the document revision actually displayedCommerce integration owner
PIM to answer sourceUpdated item retrieved without a sibling model’s compatibility textCatalogue-search owner
Change approvalNamed approver and recoverable earlier valuesProduct-data approver

Choose one owner for a failed handover, including retry and correction. Separate an export receipt from evidence that a destination saved and displayed the right record. Use the same ownership pattern across your PIM industry requirements when teams share imports or channel mappings.

Before accepting a PIM workflow, run A11 through the full handover. Require the corrected pack and source document to reach every destination, with the incompatible or unknown relationships kept distinct from manufacturer-confirmed compatibility.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup