A practical guide for physicians and institutions to frame urology product or documentation questions using clear product identity, information needs, context, and responsibility boundaries.
In brief: A well-prepared urology product enquiry is more than “send price and information”. State the purpose, product family and—where possible—the exact product code, the official document or technical information needed, the country of use, and the institutional process context. Separate clinical decisions from product/document coordination, do not send identifiable patient information, and do not assume stock, delivery, training, or technical-service availability before it is confirmed.
Define the type of enquiry first
Different objectives are often mixed in one message. What does “product information” mean in this case?
- Finding the official IFU for a specified model or component.
- Confirming a product code, packaging level, or UDI record.
- Requesting the official compatibility source for components thought to be used together.
- Locating sterility, storage, MR, or pre-use inspection information.
- Confirming the current revision for the institution’s document archive.
- Asking what product-specific educational material or support channel is currently available.
If the purpose is unclear, the recipient cannot reliably select the right record. Clinical indication, purchasing, logistics, and document-control questions should therefore be placed under separate headings with their respective owners.
How should product identity be prepared?
The manufacturer and commercial family are a starting point, not a complete identity. Transcribe the model, catalogue/reference number, component name, and available UDI-DI exactly from the package or label. Include lot, serial, or expiry information only when it is genuinely relevant and the institutional channel is appropriate. Patient name, national identifier, birth date, images, or record number are not required for a product-document request.
The European Commission explains that UDI-DI identifies a specific device model or variation and that UDI supports traceability. “Same family” therefore does not prove that two codes identify the same product or compatible components. [1]
Turn the information need into a verifiable question
Instead of “This component is compatible, correct?”, ask: “What is the current, market-applicable official compatibility source and document number for component reference ABC-123 used with system XYZ-456?” Request a link to the controlled document and, where useful, the relevant section or table. A general or verbal explanation should not displace controlled product literature.
Annex I of the EU MDR requires manufacturer information to identify the device and provide relevant intended-purpose, warning, contraindication, and safe-use information. When these fields are in question, current official IFU or controlled product literature should be the reference. [2]
Which institutional context is useful?
Useful context can be supplied without identifiable patient data:
- Requesting role: urologist, operating room, biomedical engineering, quality, procurement, or education coordination.
- Country of use and preferred document language.
- Whether the question concerns clinical selection, document control, operating-room preparation, archiving, or educational material.
- Product/document codes and revision already available.
- Requested response: official IFU link, controlled PDF identity, compatibility table, or direction to an authorised source.
- If a real deadline exists, its reason—without assuming stock or delivery commitments.
This context helps route the question to the appropriate role while preserving the institution’s internal authorisation and clinical-accountability structure.
Separate coordination responsibilities
Clinical team
The clinical team owns indication, patient suitability, interpretation of clinical risks, device selection, and follow-up. The clinical approach to penile implant selection explains why this decision cannot be reduced to ranking product features.
Operating-room, biomedical, and quality teams
These teams may contribute to identity checks, document control, storage/sterility records, equipment, and institutional procedures. The exact assignment follows the institution’s quality system.
Procurement and logistics
These functions may manage quotations, order codes, delivery, and stock information; they should not infer clinical indication or component compatibility.
Manufacturer or technical-information channel
This channel may help locate controlled product literature, explain product codes, and identify available technical material. It does not assume patient selection, clinical interpretation, or the institution’s final decision. Current service scope must be confirmed separately.
Separate documentation and education questions
“Is training available?” is ambiguous. State what is needed: label/UDI interpretation, IFU access, institutional recordkeeping, official product-use literature, or manufacturer information intended for the user. Educational material, when available, does not replace current IFU. Boston Scientific’s eLabeling portal directs users to literature from the region of the procedure and requires review before use, implantation, or follow-up care. [3]
For revision and market checks, follow the steps in the medical device documentation guide.
Practical enquiry checklist
- Purpose: one sentence explaining which decision or record needs the information.
- Product: manufacturer, family, model, component, and exact catalogue/reference code.
- Identifier: UDI-DI where available; production identifiers only when necessary and sent through an appropriate channel.
- Market: country of use, language, and relevant institution type.
- Existing literature: title/number, revision, date, and official source.
- Question: the exact section, compatibility source, or verification point requested.
- Context: requesting institutional role and responsible internal team.
- Privacy: confirmation that no patient name, identifier, image, or unnecessary clinical detail is included.
- Closure: who will evaluate the answer and how it will be entered into the institutional record.
Illustrative enquiry template
“For our institution’s technical-document archive, we would like to verify the document number and revision of the current IFU applicable in [country] for [component/model], shown on the label as [product code] within the [manufacturer/product family]. Our current copy is identified as [document number/revision]. Could you provide the controlled official source for [specific section or question]? This request contains no identifiable patient information; clinical suitability and use decisions remain with our qualified clinical team.”
This is an example only. It does not represent a commitment by Luvi to provide a particular document, product, or service.
What should be checked when the answer arrives?
- Whether the answer is explicitly tied to the product code and market asked about.
- Whether an attachment or link resolves to an official controlled source.
- Whether document number, revision, and date match the record under review.
- Whether any clinical interpretation is routed to the institution’s qualified clinical role.
- Whether unresolved questions remain visibly open instead of being closed by assumption.
Official identification resources such as FDA AccessGUDID may support checks of brand, model, and device identifier, but they do not by themselves approve a component combination, establish stock, or determine local clinical use. [4]
Frequently asked questions
Should patient history be included?
Usually not for a product-identity or documentation request. Clinicians process only necessary and institutionally authorised information in appropriate health-data systems; identifiable patient information should not be added to a general technical enquiry.
Can technical support select the device?
No. A technical-information channel may clarify product identity and access to official literature. Indication, patient suitability, and device selection remain with the qualified clinical team.
Is a telephone answer sufficient?
Critical product, compatibility, or revision information should be linked to a controlled written source under institutional procedure. The date and counterpart of a call may be recorded, but the call does not replace official literature.
Professional boundary and contact
This is general coordination guidance. It does not promise stock, delivery, a training programme, technical service, or access to a particular product on Luvi’s behalf. Clinical responsibility remains with healthcare professionals and the institution. An institutional question prepared with product and document identifiers and without identifiable patient data may be sent through the Luvi contact channel; routing and available support scope are confirmed case by case.
References
- European Commission, Unique Device Identifier — UDI.
- Regulation (EU) 2017/745 on medical devices, particularly Annex I, Section 23.
- Boston Scientific eLabeling portal.
- U.S. FDA, AccessGUDID.