The patient problem message is used to send problems from one application to another (e.g., a point of care system to a clinical repository). Many of the segments associated with this event are optional. This optionality allows systems in need of this information to set up transactions that fulfill their requirements.
Segment | Cardinality | Implement | Status |
---|---|---|---|
![]() | |||
[1..1] | SHALL | ||
v2.9 | |||
[0..1] | |||
[1..1] | SHALL | ||
![]() ![]() |
[1..*] | SHALL | |
[1..1] | SHALL | ||
![]() ![]() |
[0..1] | ||
[1..1] | SHALL | ||
[0..1] | |||
![]() ![]() |
[1..*] | SHALL | |
[1..1] | SHALL | ||
![]() ![]() ![]() |
|||
[1..1] | SHALL | B | |
[1..1] | SHALL | ||
![]() ![]() ![]() |
|||
[1..1] | SHALL | ||
![]() ![]() ![]() |
|||
[1..1] | SHALL | ||
![]() ![]() ![]() |
|||
[1..1] | SHALL | ||
![]() ![]() ![]() ![]() |
|||
[1..1] | SHALL | B | |
[1..1] | SHALL | ||
![]() ![]() ![]() ![]() |
|||
[1..1] | SHALL | ||
![]() ![]() ![]() |
|||
[1..1] | SHALL | ||
![]() ![]() ![]() ![]() |
[0..1] | ||
![]() ![]() ![]() ![]() ![]() |
[1..1] | SHALL | |
[1..1] | SHALL | ||
![]() ![]() ![]() ![]() ![]() |
|||
[1..1] | SHALL | ||
![]() ![]() ![]() ![]() ![]() |
|||
[1..1] | SHALL | ||
MSH-15 | MSH-16 | Immediate ACK | Application Ack |
---|---|---|---|
Blank | Blank | - | ACK^PC1-PC3^ACK |
NE | NE | - | - |
AL, SU, ER | NE | ACK^PC1-PC3^ACK | - |
NE | AL, SU, ER | - | ACK^PC1-PC3^ACK |
AL, SU, ER | AL, SU, ER | ACK^PC1-PC3^ACK | ACK^PC1-PC3^ACK |
This error segment indicates the fields that caused a transaction to be rejected.