Test Parameter Mapping Guide
Test parameter mapping is a critical but optional configuration step that ensures lab machine results are correctly interpreted by connected laboratory, clinical, or surveillance systems.
While LabXpert Automation can collect and display results independently, mapping becomes essential when:
- Data must flow into systems like LIS, EMR, HIS, or national health databases
- You want standardized test names across machines and systems
- Results are used in dashboards, alerts, or clinical decision support tools
This guide explains the key principles of mapping and outlines the steps required to ensure all results are reliably transmitted and understood.
🎯 Why Mapping Matters
Machines often use abbreviated, vendor-specific codes to label test results. For example:
- A CBC machine may label hemoglobin as
HGB
- A chemistry analyzer might return
CREAT
instead ofCreatinine
Without mapping, these codes may not match the identifiers used in downstream systems like:
- LIS test types and parameters
- FHIR resources
- HL7 segments
- Clinical dashboards or surveillance tools
Mapping ensures compatibility and prevents data rejection, misclassification, or loss.
🧩 What Needs to Be Mapped?
You need to map:
Machine Output | To… |
---|---|
Test panels (e.g. CBC, LFT) | Standardized test type names |
Individual parameters (e.g. HGB, ALT) | LIS or clinical system parameter codes |
Qualitative results (e.g. POS/NEG) | Agreed values (e.g. Positive/Negative) |
Units (e.g. mmol/L, g/dL) | System-expected units (if required) |
⚠️ Mapping is per-machine. Even if two machines support CBC, their parameter names may differ.
🛠️ Who Performs Mapping?
Mapping should be completed by the installation team in collaboration with:
- The facility’s lab manager or head technologist
- The LIS or HIS administrator (if applicable)
- MedX support (for complex or national integrations)
🔧 How to Map Parameters
-
Identify the Source Parameters
- Go to the Machine Detail Page in Automation.
- View a few test results to extract parameter names (e.g.
WBC
,GLU
,HGB
).
-
Get Target Codes from the System
- Access the LIS or system receiving the results.
- Locate expected codes for each parameter (e.g.
White Blood Cells
,Glucose
,Hemoglobin
).
-
Open the Mapping Interface
- In Automation, click “Manage Mappings” on the machine or system detail page.
- For each machine parameter, select the corresponding system code.
-
Save and Sync
- Save the mappings.
- Test by running a sample and verifying that results appear correctly in the downstream system.
🧠 Best Practices
- Always map the most commonly used tests first (CBC, LFT, RFT, Glucose, HIV, etc.)
- Use a consistent naming convention across facilities
- Don’t map unknown or deprecated parameters
- Review mappings after software updates or LIS migrations
- Document mappings in the deployment handover checklist
📝 Example
Machine Parameter | Mapped To LIS Parameter |
---|---|
HGB | Hemoglobin |
GLU | Glucose |
ALT | Alanine Transaminase |
WBC | White Blood Cells |
✅ Final Checklist Before Go-Live
- All machines with integrations have mappings reviewed
- Test result flows validated with actual patient samples
- Unmapped parameters documented and flagged
- Lab and LIS teams trained on how to request new mappings
If you're unsure about a mapping, contact support@labxpert.com with a screenshot of the test result and the target system.