Snapshot Mode vs. Action Code Mode
HIEBus manages allergies it finds in AL1 and IAM segments, problems it finds in DG1 and PRB segments, and procedures it finds in PR1 segments, but the interface may need to be configured with respect to how updates are managed. For certain concepts, HL7 supports either a “snapshot mode” update or an “action code” based update mechanism.
-
In snapshot mode, if a message carries any information about a concept, it is presumed to carry complete information about that concept, and HIEBus will replace prior information with the new information. To delete all existing information, the HL7 null value (
"") should be sent. -
In action code mode, an action code in the segment will determine whether a concept is removed or not; concept instances not present in a message are not deleted.
Where the HL7 specification allows, some concepts can be configured to operate in either mode. The table below specifies which ones and the default operating mode.
| Segment | Criteria used as unique identifier | Snapshot Mode | Action Code |
|---|---|---|---|
| AL1 | Patient, Encounter, Allergen Substance Code (AL1 3-1) | Default | Deletes not supported |
| IAM | Patient, Encounter, Allergen Substance Code (IAM 3-1) | Default | Supported |
| DG1 | Patient, Encounter, Diagnosis Code (DG1-3), Diagnosis Date (DG1-5.1) and Diagnosis Type (DG1-6.1) | Supported | Default |
| PRB | Patient, Encounter, Action Date/Time (PRB-2.1), Problem ID (PRB-3) and Problem Classification (PRB-10) | Supported | Default |
| PR1 | Patient, Encounter, Procedure id (PR1-3.1), Procedure Date/Time (PR1-5.1) and Procedure Type Code (PR1-6.1) | Supported | Default |
