Testing Healthcare Listener Rules - Healthcare Listener Installation and Configuration Guide

Requirements

PV1 mapping field locations have been defined in Jamf Pro.

Note:

If you want to avoid waiting for a device to wipe, setup and enroll between each test, choose Lock Device or Enable/Disable Lost Mode.

To test a rule, send an that matches the rule's event type and uses the test device's PV1 mapping field location. One of the following will occur:

If the Healthcare Listener rule deploys correctly, you can proceed to change the remote command to the command you will use in your production environment.
If the expected event does not occur, check the Jamf Pro server logs or the jamf-im.log on the Healthcare Listener server to make sure the event was received and the PV1 field matches the value entered in the mobile device’s inventory:
- The JAMFSoftwareServer.log (available in the Jamf Pro logging.html page) can provide great information about the ADT message itself, including the targeted PV1 field and the value received from the HL7 interface.
  
  Example:
  "Received A03 message with blank PV1-6-3 field value. Doing nothing. Received HCL Action: A01 with PV1-3-1 value of SUR-R6_RC.6.707_1 Received HCL Action: A03 with PV1-3-2 value of 4183 Received HCL Action: A02 with PV1-3-2 value of 2ORPACU Message [A01] with message field [PV1-3-1] value of [SUR-R6_RC.6.705_2] matched no mobile devices on mobile device field [Bedside]. No mobile device command will be queued."
- The jamf-im.log itself (available on the Healthcare Listener server) will show information about where a connection was established from, the event type, and PV1 fields specified. It will also send an ACK back to the HL7 interface.
  Example:
  "Connection Received from IP: 74.192.170.49:38033 Received A01 Message for PV1-3-1: SUR-R6_RC.6.705_2 Sending message to Jamf Pro API version 2: [com.jamfsoftware.jsam.hcl.messagequeue.HclMessageV2@381de0fd[messageType=A01 ,messageField=PV1-3-1,messageFieldValue=SUR-R6_RC.6.705_2]] JSS Response Code: HCL_ACK Connection Discarded from IP: 74.192.170.49"
If the "ADT Message" is sent over the correct port but does not originate from your approved IP range, then the jamf-im.log will display an error.
If the message does not match the ADT Event of any Healthcare Listener rule set up in Jamf Pro, the "ADT Message" will acknowledge and reject the message back to the HL7 interface.