In Epic's Identity framework, an ID Type is explicitly linked to a single Chronicles master file (e.g., EPT for patients, SER for providers). This one-to-one relationship ensures that the system knows exactly which master file to search when an ID of that type is received in a message. You cannot use a single ID Type definition to identify both a patient and a provider.

The Error Resolution Planner is a tool for triaging and planning , not for final configuration. Selecting " Suppress " within the planner indicates an intention or a decision that the error should be suppressed, but the actual administrative suppression must still be configured in the Error Code or Interface records to take effect.

XML messages are structured differently than HL7. Core components of XML include Elements (the tags that contain data), Attributes (properties provided within an element tag), and Namespaces (used to provide uniquely named elements and attributes in an XML document). " Subcomponent Separator " and " Processing ID " are specific to HL7 and are not native structural components of XML.

HL7 provides a standard set of segments (like PID for Patient Identity or MSH for Message Header).
However, to allow for site-specific data that doesn ' t fit into standard segments, HL7 reserves the letter " Z " for custom segments. Any segment starting with " Z " (e.g., ZPV, ZCD) is considered a local, non-standard extension defined by the specific healthcare organization or vendor.