Skip to content
Specialist software. Pharmacy first.
sales@pharmix.co.uk0161 818 6660
Pharmacy digital & integration teams

Keep medicine identity intact across the handover.

A product description alone is a weak connection between systems. Agree the medicine and pack identifiers, catalogue source and update process before connecting purchasing, inventory or clinical applications.

By the Pharmix product team · Reviewed
Follow the handover
  1. 01Identify the concept
  2. 02Resolve the pack
  3. 03Review changes
  4. 04Test the handover

Illustrative process—not live patient data or a clinical decision tool.

01

Distinguish the concept from the actual pack

Medicine concepts and physical supplier packs answer different questions. In a typical dm+d hierarchy, VTM, VMP, AMP and AMPP represent different levels of medicine identity. Map the level needed by the receiving workflow; a pack identifier is not interchangeable with every clinical concept.

  • Agree the identifiers required at each interface
  • Check pack sizes and units
  • Review ambiguous and missing matches
02

Catalogue maintenance is operational work

NHSBSA maintains dm+d and publishes extracted files weekly. Your installed service still needs an agreed refresh process, change review and handling for invalid or discontinued records. A successful import is not evidence that every downstream application has applied the changes.

  • Record source and imported release
  • Review invalid and discontinued identifiers
  • Define failed-import and rollback procedures
03

Interoperability needs explicit acceptance criteria

The Pharmix medicines data service can be discussed for search, mapping and application integration. Do not assume a generic FHIR or HL7 label guarantees compatibility with your specific system. Agree the message or API contract, licences, access, field mapping and error handling.

  • Named system, version and interface scope
  • Representative de-identified test records
  • Reconciliation and exception ownership
Make it specific

Bring one real workflow. Leave the patient details out.

Use de-identified examples to agree product fit, configuration, responsibilities and acceptance criteria. This guide is software procurement information, not clinical or regulatory advice.

Discuss your requirementsExplore the related product
Further reading

NHSBSA: about dm+d. This independent reference provides background, not endorsement or certification of Pharmix. Local procedures and professional responsibilities remain with your organisation.

Start with your workflow

A clearer next step for your pharmacy.

Discuss your team, stock journey or medicines data with the people building the software.

Arrange a conversation