Distribution Rules

Sections: Overview | How-To | Templates | Notes | Screenshots


Overview

As needed, Pathagility WorkPath can send data out of the system via our distribution engine. Multiple distribution rules can be configured in various ways and associated with different entities in the system:

  • Physician
  • Facility
  • Patient
  • Case type (for broader distribution at the business-needs level instead of the more focused targeted-individual level)
  • Customer (for universal distribution of every case in a customer’s environment)

Every distribution rule has three main properties, regardless of which entity it is associated with:

  1. Type of Rule: This determines both the format of the data and the method in which that data is distributed.
    • Fax: A copy of the end-clinician report is faxed to the endpoint.
    • Email: A notification is emailed to the endpoint. Each trigger status has its own notification content template, which can be one of our standard templates or a custom template designed in collaboration with a customer.)
    • FilePath: A PDF copy of the end-clinician report is delivered to the landing zone dedicated to the endpoint.
    • HL7: A custom HL7 message is transmitted to the endpoint.
    • Workpath Queue: The case is added to the queue listed in the endpoint. (This special type rearranges data within the system instead of sending data out of the system.)
  2. Status: This is the trigger for the rule, which occurs once immediately after a case has successfully entered the designated status.
    • New
    • Open
    • Canceled
    • Signed
    • Released
    • NA – On-Demand (This special status is instead triggered when the case is added to a specifically-configured queue and allows a rule to be triggered multiple times independent of case status.)
  3. Endpoint: This is directly tied to the type of rule and determines where the data is distributed to.
    • Fax: a 10-digit fax number in xxx-xxx-xxxx format
    • Email: an email address
    • FilePath: an existing FilePath queue
    • HL7: an existing FilePath queue (some HL7 interfaces will subsequently send data on to a designated SFTP landing zone)
    • WorkPath Queue: an existing WorkPath queue

Whenever a case changes status, the system checks for active distribution rules with the appropriate status trigger and entity association; all such matching rules are then processed by the distribution engine. Entities are not restricted to a single rule: each entity can have multiple rules with different configurations. For example, a facility can have a rule that sends an on-new email notification when a case associated with their facility is created as well as having a second on-release rule that faxes them a copy of the end-clinician report when a case associated with their facility is released. Additionally, a case can be associated with multiple entities that each have distribution rules. For example, a case can be associated with a physician that has an on-release fax distribution rule while also being of a case type that has an on-release HL7 distribution rule.

↑ top


How-To

To add a distribution rule for a physician, facility, or patient:

  1. Navigate to the information page for the desired entity.
  2. Scroll down to the Distribution Rules section.
  3. Click the Add Distribution Rule button on the right side of the screen.
  4. Enter the Rule Information (see details above).
  5. Click the Save button.

To edit or delete a distribution rule for a physician, facility, or patient:

  1. Navigate to the information page for the desired entity.
  2. Scroll down to the Distribution Rules section.
  3. Based on the desired action…
    • Disable: Click the Disable icon in the Action column for the desired enabled rule.
    • Enable: Click the Enable icon in the Action column for the desired disabled rule.
    • Delete: Click the Delete icon in the Action column for the desired rule.

↑ top


Templates

In addition to our standard templates, custom templates can be designed in collaboration with a customer. All notification content templates are based on trigger status:

  • Status: New
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has created a new case for “{Patient Name}”.
     
    Accession #: {Accession ID}
    Type: {Case Type Description}
    Created: {Added Date}
    Created By: {Added By}
     
  • Status: Open
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has modified case {Accession ID}.
     
    Accession #: {Accession ID}
    Patient: {Patient Name}
    Status: {Status}
    Type: {Case Type Description}
    Created: {Added Date}
    Created By: {Added By}
    Last Modified: {Modified Date}
    Modified By: {Modified By}
     
  • Status: Canceled
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has canceled case {Accession ID}.
     
    Accession #: {Accession ID}
    Patient: {Patient Name}
    Status: {Status}
    Type: {Case Type Description}
    Created: {Added Date}
    Created By: {Added By}
    Last Modified: {Modified Date}
    Modified By: {Modified By}
     
  • Status: Signed
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has completed case {Accession ID}. The results will be available shortly.
     
    Accession #: {Accession ID}
    Patient: {Patient Name}
    Type: {Case Type Description}
    Created: {Added Date}
    Created By: {Added By}
    Completed: {Signed Date}
    Completed By: {Signed By}
     
  • Status: Released
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has released case {Accession ID}. The results are available in all of your distribution channels.
     
    Accession #: {Accession ID}
    Patient: {Patient Name}
    Type: {Case Type Description}
    Created: {Added Date}
    Created By: {Added By}
    Signed: {Signed Date}
    Signed By: {Signed By}
     
  • Status: NA – On-Demand
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has performed work on case {Accession ID}.
     
    Accession #: {Accession ID}
    Patient: {Patient Name}
    Status: {Status}
    Type: {Case Type Description}
    Created: {Added Date}
    Created By: {Added By}
    Last Modified: {Modified Date}
    Modified By: {Modified By}
     

For distribution rules associated with a patient entity, these templates are substituted for new and released cases:

  • Status: New (patient-associated)
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has started to process a test for {Patient Name}.
     
    The results will be available soon. This email address will be notified when they are ready to review.
     
    Accession #: {Accession ID}
    Type: {Case Type Description}
    Created: {Added Date}
    Created By: {Added By}
     
  • Status: Released (patient-associated)
    Subject: [{Customer Name}] Case Information: {Accession ID}
    Body:This is a notification to inform you that {Customer Name} has released case {Accession ID}. The results can be viewed at the following address: {Direct Link via Patient Portal}
     
    Accession #: {Accession ID}
    Patient: {Patient Name}
    Created: {Added Date}
    Created By: {Added By}
    Signed: {Signed Date}
    Signed By: {Signed By}
     

↑ top


Notes

  • Distribution rules for patients are only available if the WorkPath Patient Portal has been enabled and configured by Pathagility Support.
  • By default, the distribution engine is disabled in beta environments (rules can be created and triggered, but no data will leave the system). If you would like to test distribution in a beta environment, please contact Pathagility Support to discuss details and schedule a testing window.
  • Please contact Pathagility Support for help in adding FilePath and HL7 rules or any type of rule with a Case Type or Customer association — additional configuration may be required.

↑ top


Screenshots

Distribution Rules: Add Rule
Distribution Rules: Add Rule

Distribution Rules: Rule Information
Distribution Rules: Rule Information

Distribution Rules: Actions
Distribution Rules: Actions

↑ top

0