Lookup Manager
Manage the lookup tables your channels reference, right in WebAdmin.
Why it matters
One home for reference data.
Integration teams end up with the same crosswalks pasted into transformer scripts and the same code tables duplicated across channels, where every change means editing and redeploying. Lookup Manager centralizes that reference data: one managed lookup group per data set, edited in WebAdmin, read and written by your channels at runtime. Update a mapping in one place and every channel that uses it picks up the change, with caching for speed and a history of who changed what.
Capabilities
What it does:
Centralized reference data
Billing codes, provider directories, and code crosswalks live in managed lookup groups instead of hardcoded scripts or ad hoc SQL.
Real-time channel access
Read and write lookup data from transformers and code templates through the LookupHelper functions, or externally from any system through the REST API.
JSON values with indexed search
Store plain strings or JSON documents, index fields like npi or address.city, and search them without scanning the whole group.
Per-group caching
Configurable in-memory caching (LRU or FIFO) for each group, with hit and miss statistics for tuning performance.
Full audit trail
Every value change is recorded and searchable on the group's History tab.
Import and export
Bulk-load or back up a group's values as CSV, or a complete group as JSON.
How it works
Get started in minutes.
- 1
Create a lookup group
Name the group and choose its value type: TEXT for plain strings, or JSON for structured documents with indexed fields.
- 2
Load your values
Add key-value pairs by hand, or bulk-import values from CSV (or a complete group as JSON).
- 3
Call it from your channels
Read and write values in transformers and code templates with the LookupHelper functions, or from external systems through the REST API.
- 4
Tune and audit
Watch each group's cache hit rate, adjust its size and eviction policy, and trace every change on the History tab.
Requirements
What you'll need:
- BridgeLink 26.6.0 or later
- For JSON value groups: an external database (PostgreSQL 9.4+, MySQL 8.0+, Microsoft SQL Server, or Oracle 12.2+). TEXT groups work with any database, including the default Derby
- With the Advanced Access Control plugin: a role that carries the Lookup Manager permission. Without that plugin, no permission setup is needed
FAQ
Frequently asked questions.
Do I need to install anything?
No. Lookup Manager is included in BridgeLink 26.6 and appears in WebAdmin. If your organization uses the Advanced Access Control plugin, an administrator assigns the Lookup Manager permission to your role.
What kind of data belongs in it?
Key-value reference data your channels depend on: billing codes, provider directories, and code crosswalks between systems. One managed lookup group per data set, instead of mappings hardcoded in JavaScript or scattered across ad hoc SQL.
How do channels use lookups?
Transformer steps and code templates read and write values at runtime through the LookupHelper functions, and external systems can use the REST API. JSON values are returned as raw JSON text, so a script parses them with JSON.parse() before reading fields.
What's the difference between TEXT and JSON groups?
TEXT stores any string and works with every database. JSON validates each value as well-formed JSON on write and can index named fields, like npi or address.city, for direct search, and it requires an external database such as PostgreSQL, MySQL, SQL Server, or Oracle.
Is there an audit trail?
Yes. Every value change is recorded and searchable on the group's History tab, and each group reports cache hit and miss statistics.
Availability
Included with BridgeLink, with no separate download or license. TEXT lookup groups work with any database; JSON groups require an external database.
Add Lookup Manager to BridgeLink.
Talk to us about your deployment, or read the full user guide to get started.