Q: What does it mean to “re-map” a Discharge Type?
A:
Re-mapping a Discharge Type means updating the connection between the EMR field and the corresponding CRM field so the values sync correctly.
This is usually needed when:
A new discharge type is created in the EMR
An existing discharge type is renamed
The discharge type field is moved to a new form or tab inside the EMR
Reporting in the CRM no longer reflects the expected discharge values
Q: If we change the Discharge Type form in the EMR, will it automatically update in the CRM?
A:
Not always.
If the discharge field is moved to a new form, renamed, or recreated in the EMR, the original mapping may no longer apply. Even if the label looks the same, the underlying field ID in the EMR could be different.
In those cases, the CRM may:
Stop receiving discharge updates
Receive incomplete data
Continue referencing the old field
A mapping review is recommended anytime structural changes are made inside the EMR.
Q: How can I tell if the Discharge Type is not syncing correctly?
A:
Common signs include:
Discharge Type not updating in the CRM after discharge in the EMR
Reports showing blank or outdated discharge values
Only some discharge types syncing correctly
If reporting appears inconsistent after changes were made in the EMR, the mapping should be reviewed.
Q: What needs to match between the EMR and the CRM?
A:
For clean syncing:
The discharge types enabled in the EMR must also exist in the CRM.
The field being used in the EMR must be the same field that is mapped in the integration settings.
The value options should align (including spelling and formatting where applicable).
If ne
w discharge types were added in the EMR, they may also need to be added in the CRM to avoid sync gaps.
Q: When should Support be involved?
A:
Support should review the mapping when:
A new discharge form or tab is introduced in the EMR
Discharge types were recently restructured
Syncing stopped after configuration changes
Reporting accuracy is critical and needs confirmation
A quick mapping review can confirm whether everything is aligned before reporting discrepancies occur.
Pro Tips / Extra Help
Before requesting a remap, gather the following:
The exact name of the discharge field currently being used in the EMR
A list of active discharge types
The approximate date when changes were made
This helps determine whether the issue is configuration-related or mapping-related.
If unsure whether changes impact the integration, it’s best to review proactively rather than wait for reporting discrepancies.
Related Resources
EMR Integration Overview
Field Mapping Best Practices
Troubleshooting Sync Discrepancies
CRM Reporting Configuration Guide