Overview
When iSalus OfficeEMR submits immunization records to a state immunization registry, the outbound HL7 2.5.1 message must include a facility identifier that the registry can match to the submitting practice. This identifier is assigned by the registry and must be entered in iSalus before submissions will be accepted.
The facility identifier appears in two fields of the HL7 message:
| HL7 Field | Segment Location | Purpose |
|---|---|---|
| MSH-4 | MSH|...|...|...|{value}|... |
Sending facility — identifies the organization submitting the message to the registry. |
| RXA-11 | RXA|...|^^^^{value}~~~L|... |
Administered-at location — identifies where the immunization was given. Most registries validate this field to authorize the submission. |
Configure Location in the Setup > Location Screen
The facility identifier is configured at the location level in iSalus. Each physical location that submits immunizations must be configured separately.
Navigation
Instructions
- Open the Setup Portal in iSalus OfficeEMR.
- Click Locations.
- Search for and open the location record to be configured.
- Within the location record, click the Immunization Export Setup link. This is a secondary configuration section within the location form.
- The Immunization Export Setup dialog contains two fields:
Field What to Enter MSH 4 The registry-assigned facility identifier for this location. Enter the exact value provided by the state registry (e.g., a SIIS ID, OID, or alphanumeric facility code). RXA 11 Enter the same registry-assigned facility identifier. This is the value that most registries actively validate on inbound messages. - Verify that your expected values are populated in the MSH 4 and RXA 11 fields.
- Click OK to save.
- After updating, verify the practice output when records are submitted via Reports > Immunization Export report.
- Repeat for every location at the practice that submits immunizations to a registry.
Finding the Registry-Assigned Facility Identifier
The facility identifier must come from the state registry — this value is not generated by or known by iSalus. General registry guidance:
- Log in to the state registry's portal for the practice.
- Navigate to the practice or facility profile.
- Locate the facility identifier, SIIS ID, organization ID, or equivalent field. The format varies by registry.
- If the value is not visible in the portal, contact the state registry's support team directly to inquire on how to obtain the necessary information.
Review Related Company Settings
The following company settings (Patient > Patient Export Settings) control how the facility identifier is formatted and placed within the outbound HL7 message. Review these settings to confirm they are aligned with the requirements of the registry the practice is submitting to.
Company Settings Quick Reference
| Setting | Recommended Value | Impact |
|---|---|---|
| HL7 Immunization Export 2.5.1 RXA-11 | 2 |
Facility ID placed in RXA-11.4 — required by most registries. |
| Push MSH-4 value into RXA-11.4 | true |
MSH-4 automatically copied to RXA-11.4, keeping both fields in sync. |
| Sending Facility (MSH-4) — company level | ^^ (empty) |
When blank, each location's Immunization Export Setup drives MSH-4. |
| Receiving Facility (MSH-6) | Registry-provided | Identifies the destination registry. Provided during onboarding. |
| Send Ordering Physician NPI in ORC-12 | Per registry requirement | Sends provider NPI in ORC-12 instead of internal iSalus provider ID. |
| Send Ordering Physician NPI in RXA-10 | Per registry requirement | Sends provider NPI in RXA-10 instead of internal iSalus user ID. |
More Details for Related Company Settings
HL7 Immunization Export 2.5.1 — RXA-11
Controls which sub-field of RXA-11 receives the facility identifier.
| Value | Behavior | Notes |
|---|---|---|
0 |
Populate RXA-11.1 | Places the facility ID in the Point of Care sub-field. Not accepted by most state registries. |
1 |
Do not populate | RXA-11 is left empty. Use only if the registry explicitly does not require a facility ID in this field. |
2 |
Populate RXA-11.4 | Recommended. Places the facility ID in the Facility sub-component (RXA-11.4). Required by most state registries. |
HL7 Immunization Export 2.5.1 — Push MSH-4 Value into RXA-11.4
When enabled, iSalus automatically copies the MSH-4 value into RXA-11.4, so both fields are populated from a single source — the location record's Immunization Export Setup.
| Value | Behavior |
|---|---|
true |
Recommended. The MSH-4 value (sourced from the location record) is automatically pushed into RXA-11.4 on every outbound message. Both fields stay in sync. |
false |
MSH-4 and RXA-11.4 are populated independently. The RXA-11 field in the location's Immunization Export Setup must be manually maintained. |
HL7 Immunization Export 2.5.1 — Sending Facility (MSH-4)
A company-level override for MSH-4. Accepts a three-part value: NamespaceID^UniversalID^UniversalIDType.
| Value | Behavior |
|---|---|
^^ (empty) |
Recommended for multi-location practices. When blank, MSH-4 is sourced per-location from the Immunization Export Setup, allowing each location to carry its own facility identifier. |
| Populated value | If populated, this value overrides the location record for all locations company-wide. Appropriate only if all locations share a single registry facility identifier. |
HL7 Immunization Export 2.5.1 — Receiving Facility (MSH-6)
Defines the destination registry endpoint in the MSH-6 field. Accepts a three-part value: NamespaceID^UniversalID^UniversalIDType. This value is provided by the state registry during onboarding and is the same for all practices submitting to that registry.
HL7 Immunization Export 2.5.1 — Send Ordering Physician NPI in ORC-12
When true, places the ordering provider's NPI in ORC-12.1 and ORC-12.3 instead of the iSalus internal provider ID. Does not affect facility ID fields, but may be required by registries that mandate NPI-based provider identification.
HL7 Immunization Export 2.5.1 — Send Ordering Physician NPI in RXA-10
When true, places the ordering provider's NPI in RXA-10.1 and RXA-10.3 instead of the iSalus administering user ID. Does not affect facility ID fields but contributes to full message compliance for NPI-required registries.
