Diagnosing Data Not Going to RADAR

Owned by George Swinnerton
Jan 17, 2018
1 min read

1)

Check the file has been received by HealthShare and there were no errors in the PV Processing

See Searching for PV Messages

2)

Check that the data you expect has made it to PV.

3)

Check that the data you expect has made it into HealthShare

4)

Check that a ProgramMembership exists for this patient - Managing Program Membership

5)

Disable PVFeed and PVFeed_Direct and wait a few minutes. This allows you to see easily messages that are triggered across Namespaces.

a) Find the latest message for the Patient as #1 and re-submit it. Check that it processes successfully within the PV Namespace.

b) Go into the HSEDGE1 Namespace and check that there are no errors.

c) Check that a message has been sent to the Subscription Operation. This is the notification that the record has been updated which triggers the check for matching Subscriptions.

d) Go to the HSACCESS namespace and check whether Renal.Process.RadarImportProcess has received a message. This means the Subscription has triggered correctly.

e) Still in the HSACCESS namespace check the Renal.Operation.RadarImportProcess has received a message. This means it has sent something to RADAR.


6)

If the data still hasn't appeared in RADAR check in the RADAR logs to make sure it hasn't been rejected for being incomplete etc.