| event_type |
Input |
A string comprised of an HL7 message type and an HL7
event type separated by a "^".
The value must be defined in the list of known VDEF message type/event type
combinations in file 577.
Example: "ADT^A28"
|
name_value_pairs |
Input |
A string comprised of the following format:
SUBTYPE=<text>^IEN=nn where the Subtype text is a code based on the
application's domain and the clinical event and the IEN is the IEN of the
primary file associated with the event.
All Subtype names must be defined for this Message Type/Event Type in the VDEF
EVENT DESCRIPTION file (#577). The name "SUBTYPE" is reserved for the purposes
of uniquely identifying the request sub-type when more than one VDEF Event is
defined for a Message Type/Event Type combination. For example, the HL7
message type/event ORU^R01 is used by multiple VistA domains to send
unsolicited results. In these cases, the Subtype is used to differentiate the
sending domain's unique message contents within the structure of the ORU^R01.
Example: "SUBTYPE=VTLS^IEN=12345"
|
text_message |
Both |
Acceptance or rejection text returned by the VDEF
API.
Example: "Invalid event type."
|
$$QUEUE |
Output |
1 if the HL7 request was queued up for processing
0 if it was not queued up for processing
|