Mapping ASC Preference Cards to FHIR SupplyRequest

Mapping ASC preference cards to FHIR SupplyRequest creates a direct data bridge between surgical scheduling and autonomous procurement, ensuring each case receives the exact supplies without manual entry. By aligning the card's item list, quantities, and timing with the standardized SupplyRequest fields, operations teams can feed reliable data into the ordering engine.

The process starts with a detailed review of the card structure, then matches each element to its FHIR counterpart, validates the transformed payload, and generates compliant SupplyRequest resources. Finally, the resources are injected into the autonomous procurement workflow, and a governance routine keeps the mapping current as cards evolve.

Understand the Preference Card Structure

ASC preference cards list the supplies needed for each procedure. Typical columns include:

• Item Name – the product description used by the supplier.
• Size / Variant – e.g., 5 mm trocar, 10 cm catheter.
• Quantity – how many units are required per case.
• Supplier – contract‑preferred vendor or fallback.

Many centers add custom fields to capture local workflow:

• Bundle Code – a code that groups items into a kit.
• Surgeon Preference – notes such as "Dr. Lee prefers reusable sutures".
• Room – specific operating rooms where the card applies.

Identify the source format before building a mapping pipeline. Common sources are:

1. Excel workbook with multiple sheets, formulas, and drop‑down lists.
2. CSV export from the ASC’s inventory system.
3. Paper cards that are scanned and processed with OCR.

Record the storage location – network share, cloud folder, or EMR attachment – so the integration can retrieve the file consistently.

Column	Example
Item Name	Hemostat, 10 cm
Size / Variant	10 cm
Quantity	2
Supplier	MedSupply Co.
Bundle Code	BK‑2023‑A

Match Card Elements to FHIR SupplyRequest Fields

Mapping elements from preference cards to FHIR SupplyRequest fields requires attention to detail. Here are the key mappings:

• Item Name: The item name from the preference card should be mapped to SupplyRequest.itemCodeableConcept.text. For instance, if the preference card lists "Surgical Drapes," this should directly populate the text field.
• Size or Variant: This information should be mapped to SupplyRequest.itemCodeableConcept.coding. Use appropriate codes such as UDI or SNOMED. If the drapes are available in different sizes, the specific size can be coded accordingly to ensure compliance and traceability.
• Quantity: The required quantity should populate both SupplyRequest.quantity.value and SupplyRequest.quantity.unit. If the preference card specifies "10 units" of surgical drapes, then value would be set to 10 and unit to "units".
• Supplier Contract ID: Each item should reference the supplier contract ID in SupplyRequest.dispenseRequest.performer. If the surgical drapes are supplied under contract ID "CONTRACT123", this ID needs to be included to ensure proper fulfillment.

Here’s a checklist for mapping:

Preference Card Element	FHIR SupplyRequest Field
Item Name	itemCodeableConcept.text
Size/Variant	itemCodeableConcept.coding
Quantity	quantity.value, quantity.unit
Supplier Contract ID	dispenseRequest.performer

Prepare Data for Validation

Preparing data for validation is a key step in mapping preference cards to FHIR SupplyRequest resources. Start by standardizing product names using the ASC item master to avoid duplicates. This creates a consistent reference for each item used in surgical procedures.

Next, verify each Unique Device Identifier (UDI) against the FDA Global UDI Database. This confirms that all products comply with regulatory standards. For example, if a preference card lists a specific surgical instrument, check its UDI to ensure it is valid and registered.

Additionally, ensure that all codes used in the preference cards belong to recognized terminology systems, such as SNOMED CT or LOINC. This guarantees that the data is interoperable and can be understood universally.

To facilitate this process, consider using a checklist:

• Standardize product names from the ASC item master.
• Verify each UDI against the FDA Global UDI Database.
• Ensure all codes are from SNOMED CT or LOINC.
• Flag any missing or ambiguous entries for manual review.

For further assistance, refer to our guide on auditing ASC item masters for duplicate UDI records.

Generate SupplyRequest Resources

To generate SupplyRequest resources, use a script or a low-code tool that reads the cleaned CSV file containing your mapped preference card data. This process converts the data into JSON bundles compatible with the FHIR standard.

Apply a reusable template that inserts the mapped fields into the FHIR SupplyRequest structure. This template should include essential elements such as:

• status: Set the status to 'active'.
• intent: Define the intent as 'order'.
• identifier: Include a unique identifier, such as the preference card ID, in the SupplyRequest.id field for traceability.
• item: Map each item from the preference card to the appropriate FHIR SupplyRequest item fields.

Here’s a simplified example of what a JSON bundle might look like:

{ "resourceType": "SupplyRequest", "id": "prefCard-1234", "status": "active", "intent": "order", "item": [ { "code": { "coding": [ { "system": "http://example.org/fhir/medications", "code": "med-001" } ] }, "quantity": { "value": 1 } } ] }

Once the JSON bundles are generated, save each one to a staging folder. This folder will serve as the location for import into your autonomous procurement system, ensuring a streamlined workflow for operational efficiency.

Integrate with the Autonomous Procurement System

To integrate with the autonomous procurement system, begin by uploading the generated JSON bundles through the system’s API endpoint designed for bulk SupplyRequest ingestion. Ensure that each SupplyRequest follows the correct format to avoid errors during the upload process.

Next, configure the system to match incoming SupplyRequests with existing contracts. Set parameters that align with your organization’s specific agreements and regulatory checks. Verify that each item complies with applicable standards.

As you proceed, monitor the import log for any rejected resources. This log will highlight issues such as mismatched items or missing contract details. Address these promptly to maintain an efficient workflow. Here’s a checklist to help with monitoring:

• Check for error messages in the import log.
• Identify the reasons for rejection (e.g., contract mismatch, regulatory non-compliance).
• Resolve issues by updating the corresponding SupplyRequest or contract details.
• Re-attempt the upload of corrected requests.

Finally, run a pilot with a single operating room (OR) schedule. This will help confirm the integration flow. Monitor the procurement process closely during the pilot to ensure that the system operates as expected, identifying any further adjustments needed before full-scale implementation. Once validated, you can leverage the capabilities of mintHealth to streamline your procurement operations.

Maintain and Update the Mapping

To ensure the mapping of preference cards to FHIR SupplyRequest remains accurate and effective, regular maintenance and updates are essential.

First, schedule quarterly reviews of the item master. This process helps identify new products that should be added and discontinued items that need to be removed. Keeping the item master current ensures that the procurement system reflects the latest offerings.

When new coding standards are adopted, such as the EU MDR, update the mapping template accordingly. This ensures compliance with regulatory requirements and maintains the integrity of your data.

Document all changes in a version-controlled repository. This practice keeps the team aligned and allows for easy tracking of modifications over time. Version control also facilitates collaboration among team members, ensuring everyone is informed about the latest updates.

For onboarding new materials managers, provide training focused on the extraction and upload steps for the mapping process. A checklist can aid in this training:

• Review preference card structure and FHIR SupplyRequest fields.
• Understand the process for identifying new or discontinued items.
• Learn how to update the mapping template with new coding standards.
• Practice documenting changes in the version-controlled repository.
• Complete a mock extraction and upload session.

Implementing these strategies keeps the mapping process responsive to changes in product offerings and regulations.