Sample Data

An InterSystems® Healthcare Action Engine demo instance initializes sets of example triggers, rules, and cards (as well as example message templates and notification policies for asynchronous notifications). A demo instance also provides a set of files which contain sample patient data in the <durable-hs-data-ingestion> directory. Together, these elements constitute functioning example notification workflows which you can engage from a client application: the patient data in each file returns a particular result when it is evaluated by a particular rule. See Get Started to learn how your client applications can execute a Healthcare Action Engine synchronous interaction using this demo data.

Sample Data for Synchronous Notifications

For synchronous notifications, the patient data files are HL7 files. For each rule you want to trigger at its service endpoint, you must import the contents of the corresponding patient file into your FHIR server. (Alternatively, you can incorporate the data within the prefetch object of the service request.)

Synchronous Notification Demo Production Data Files

The example patient HL7 files correspond with example synchronous notification rules and card results as summarized below:

Note:

The Relevant Rule column lists the rule that returns a card based on the given patient’s data, except for the negative test cases, which should return no cards. Patient files with an expected negative test cast have the suffix -NoCardReturn.hl7.

EDSDemoAntiplateletForCAD.hl7

Patient	Peter Johnson
Description	Age over 18, chronic ischemic heart disease, not on Aspirin or clopidogrel
Relevant Rule/Service	EDSDemoAntiplateletForCAD
Card Return	EDS Demo CAD Not on Aspirin

EDSDemoCMS145v7.hl7

Patient	Quinton Perez
Description	Age over 18, chronic ischemic heart disease, unspecified systolic (congestive) heart failure, not prescribed Beta Blocker
Relevant Rule/Service	EDSDemoAntiplateletForCAD
Card Return	EDSDemoCMS145v7

EDSDemoDiabetesPossiblyUncontrolled.hl7

Patient	EDSDemoCMS145v7
Description	Type 2 diabetes mellitus with unspecified complications, Hemoglobin A1C 7.8%, on metformin hydrochloride 500 MG
Relevant Rule/Service	EDSDemoDiabetesPossiblyUncontrolled
Card Return	EDSDemo Diabetes Alert

EDSDemoElevatedINR.hl7

Patient	George Holman
Description	Lab Prothrombin time (PT) 4.0
Relevant Rule/Service	EDSDemoElevatedINR
Card Return	EDSDemo INR greater than 3.5

EDSDemoScreeningColonoscopyWithProcLongerThan10Years.hl7

Patient	Jose Lopez
Description	Age over 50, last colonoscopy over 10 years ago
Relevant Rule/Service	EDSDemoScreeningColonoscopy
Card Return	EDSDemo Screening Colonoscopy

EDSDemoScreeningColonoscopyWithProcWithinLast10Year-NoCardReturn.hl7

Patient	John Edison
Description	Age over 50, last colonoscopy within last 10 years
Relevant Rule/Service	EDSDemoScreeningColonoscopy
Card Return	N/A

EDSDemoScreeningOsteoporosisWithNoDXA.hl7

Patient	Michelle Williams
Description	Female between 65 and 85, no dual energy X-ray absorptiometry of hip (DXA)
Relevant Rule/Service	EDSDemoScreeningOsteoporosis
Card Return	EDSDemo Osteoporosis Screening

EDSDemoScreeningOsteoporosisWithWDXAServiceRequest-NoCardReturn.hl7

Patient	Diana Beth
Description	Female between 65 and 85, with dual energy X-ray absorptiometry of hip (DXA)
Relevant Rule/Service	EDSDemoScreeningOsteoporosis
Card Return	N/A

EDSDemoUncontrolledDiabetesWarning.hl7

Patient	Jill Aguilar
Description	Diabetes mellitus, cholesterol in LDL in Serum or Plasma by calculation: 140 mg/dl
Relevant Rule/Service	EDSDemoUncontrolledDiabetes
Card Return	EDSDemo Diabetes alert

EDSDemoUncontrolledDiabetesCritical.hl7

Patient	Olivia James
Description	Diabetes mellitus, cholesterol in LDL in Serum or Plasma by calculation: 155 mg/dl
Relevant Rule/Service	EDSDemoUncontrolledDiabetes
Card Return	EDSDemo Diabetes alert -critical

EDSDemoUndiagnosedDiabetes.hl7

Patient	Emma Wood
Description	On insulin glargine, missing diabetes diagnosis
Relevant Rule/Service	EDSDemoUndiagnosedDiabetes
Card Return	EDSDemo Undiagnosed diabetes

EDSDemoVaccineMeningococcalMoreThan1YrAgo.hl7

Patient	Janet Jackson
Description	Age 12–16, vaccinated with meningococcal ACWY, unspecified formulation over a year ago
Relevant Rule/Service	EDSDemoVaccineMeningococcal
Card Return	EDSDemo DueForMeninggococcal Vaccine

EDSDemoVaccineMeningococcalWithinLastYear-NoCardReturn.hl7

Patient	David Parker
Description	Age 12–16, vaccinated with meningococcal ACWY, unspecified formulation within a year ago
Relevant Rule/Service	EDSDemoVaccineMeningococcal
Card Return	N/A

EDSDemoCMS135v7.hl7

Patient	Ted Johnson
Description	Age over 18, unspecified systolic heart failure, not on ACE or ARB
Relevant Rule/Service	EDSDemoCMS135v7
Card Return	EDSDemoCMS135v7 Card

EDSDemoCMS135v7WithMed-NoCardReturn.hl7

Patient	Larry Johnson
Description	Age over 18, unspecified systolic heart failure, on Lisinopril
Relevant Rule/Service	EDSDemoCMS135v7
Card Return	N/A

EDSDemoPalivizumabPriorAuth.hl7

Patient	Stanley Lee
Description	Requisite conditions can be found hereOpens in a new tab under “Medical Necessity”.
Relevant Rule/Service	EDSDemoPalivizumabPriorAuth
Card Return	EDSDemo Palivizunab_approve

EDSDemoCrCl60.hl7 *

Patient	Abby Stone
Description	Age 50, creatinine renal clearance measure of 60 mL/min
Relevant Rule/Service	EDSDemoCiproRenalDose
Card Return	N/A

EDSDemoCrCl45.hl7 *

Patient	Barbara Stone
Description	Age 50, creatinine renal clearance measure of 45 mL/min
Relevant Rule/Service	EDSDemoCiproRenalDose
Card Return	EDSDemo Cipro renal dose adjustment

EDSDemoCrCl15.hl7 *

Patient	Delilah Stone
Description	Age 50, creatinine renal clearance measure of 15 mL/min
Relevant Rule/Service	EDSDemoCiproRenalDose
Card Return	EDSDemo Cipro renal dose adjustment 5-29

EDSDemoCrCl3.hl7 *

Patient	Emily Stone
Description	Age 50, creatinine renal clearance measure of 3 mL/min
Relevant Rule/Service	EDSDemoCiproRenalDose
Card Return	EDSDemo Cipro renal dose adjustment less than 5

Note:

The patient files marked with an asterisk (*) provide test cases for the rule EDSDemoCiproRenalDose, which is based on the order-select trigger. The Healthcare Action Engine Demo Walkthrough Postman collection includes requests (numbered A1 through A3) which demonstrate a service interaction which executes this rule.

The interaction is similar to the one described in Execute a Complete Service Call:

Set the value of the orderSelectPatient collection variable with the ID for one of the patients.
Update the hooksToken and fhirAccessToken collection variables with the values provided in the response bodies for the requests A1. Acquire CDS Hooks Token for Order-Select Request and A2. Acquire New FHIR Fetch Token (Same as 3), respectively.
Send the request A3. Order-Select Request to execute the rule.

Sample Data for Asynchronous Notifications

Important:

Healthcare Action Engine version 2023.2 includes asynchronous notification functionality for limited customer testing only. Further development may substantively change how users should implement asynchronous notifications within their systems.

When used only for testing, there is no potential for patient harm and so this experimental feature is not yet included in the scope of clinical safety assessment and publications. Use of this experimental feature for any purpose other than product testing is prohibited.

If you have configured the experimental asynchronous notification feature available in this version of the Healthcare Action Engine prior to running InstallDemo(), your Healthcare Action Engine demo instance also includes additional data to simulate asynchronous notifications in response to several example patient admissions.

Using this data, you can trigger an active notification policy in response to a simulated admission event by following a procedure similar to the one described in Sample Data:

If you would like to test the delivery of a notification to an active email address, use a text editor to open the demo file for recipient determination groups (<durable-hs-data-ingestion>/EDSDemoGroupData.csv) and replace the placeholder email address for the relevant group’s contact with the email address where you would like the Healthcare Action Engine to deliver the notification. Then, import the modified group file. (If you skip this step, notification delivery fails but Healthcare Action Engine still logs the delivery attempt.)
In the <durable-hs-data-ingestion> directory, locate the XML file which corresponds to the admission scenario you want to simulate. (Each XML file contains data from an HL7® V2 ADT message, in SDA format.)
Move or copy the XML file to the /SDAIn directory for your Edge Gateway.

Asynchronous Notification Demo Data Files

The demo production includes demo data to simulate asynchronous notifications in several scenarios. Each XML file is described below.

EDSDemoPatientA.xml

Patient Admitted	Anthony Martin, a member of Dr. Smith’s PCP Patients group
Notification Policy	NotifyFHIR
Rule	EDSDemoAdmission
Card Return	EDSDemoAdmission
Contact Notified	Dr. Smith
Message Template	DemoEmailTemplate

EDSDemoPatientB.xml

Patient Admitted	Brenda Anderson, a member of the High Risk Patients group
Notification Policy	NotifyFHIR
Rule	EDSDemoAdmission
Card Return	EDSDemoAdmission
Contact Notified	Social Worker Christina
Message Template	DemoEmailTemplate

EDSDemoPatientC.xml

Patient Admitted	Colin Widener, a member of a group of patients with a High-risk Psych Diagnosis
Notification Policy	NotifyFHIR
Rule	EDSDemoAdmission
Card Return	EDSDemoAdmission
Contact Notified	. Psych NP Rose
Message Template	DemoEmailTemplate

EDSDemoPatientD.xml

Patient Admitted	Donna Winters, a patient in the University Podiatry Practice group who is diabetic, and who is diagnosed with lower extremity cellulitis
Notification Policy	DiabetesLECellulitisFullPHI
Rule	EDSDemoDiabetesAndLECellulitis Note: The EDSDemoDiabetesAndLECellulitis rule returns a different card (EDSDemoDiabetesAdmission) in response to the admission of a patient who is diabetic but who does not have a diagnosis of lower extremity cellulitis. However, none of the sample XML files simulate the admission of a patient who meets these criteria.
Card Return	EDSDemoDiabetesAndLECellulitis
Contact Notified	. University Podiatry Pool
Message Template	WarningLevelEmailFullPHI Note: You can customize these notification policies to use an alternative message template, WarningLevelEmailLimitedPHI, which incorporates less of the patient’s personal health information into the message.

EDSDemoPatientE.xml

Patient Admitted	Ernest Barnes, a patient in the Community Podiatry Practice group who is diabetic, and who is diagnosed with lower extremity cellulitis
Notification Policy	DiabetesLECellulitisFullPHI
Rule	EDSDemoDiabetesAndLECellulitis Note: The EDSDemoDiabetesAndLECellulitis rule returns a different card (EDSDemoDiabetesAdmission) in response to the admission of a patient who is diabetic but who does not have a diagnosis of lower extremity cellulitis. However, none of the sample XML files simulate the admission of a patient who meets these criteria.
Card Return	EDSDemoDiabetesAndLECellulitis
Contact Notified	Community Podiatry Pool
Message Template	WarningLevelEmailFullPHI Note: You can customize these notification policies to use an alternative message template, WarningLevelEmailLimitedPHI, which incorporates less of the patient’s personal health information into the message.

The patients and the contacts in the XML files are also referenced in the demo file for recipient determination groups. In the demo group file, each patient is a member of a particular group. The contact notified when you simulate the admission of that patient is the managing entity of the group to which the patient is assigned

Demo File for Importing Recipient Determination Groups

The <durable-hs-data-ingestion> directory for your Healthcare Action Engine demo production contains a file named EDSDemoGroupData.csv which demonstrates the expected format for the comma-separated value (.csv) file you must use to import an asynchronous notification group file. As is, it contains the group data required to test the asynchronous notification feature.

The EDSDemoGroupData.csv file contains the following information:

GRP,1001,Dr. Smith's PCP Patients,Dr. Smith,email,drsmith@email.org
MBR,100001001,Martin,Anthony
GRP,1002,High-risk Patients,Social Worker Christina,email,christina@email.com
MBR,100001002,Anderson,Brenda
GRP,1003,High-risk Psych Diagnosis,Psych NP Rose,email,nprose@email.com
MBR,100001003,Widener,Colin
GRP,1004,University Podiatry Practice,University Podiatry Pool,email,universitypod@email.com
MBR,100001004,Winters,Donna
GRP,1005,Community Podiatry Practice,Community Podiatry Pool,email,communitypod@email.com
MBR,100001005,Barnes,Ernest

The patients and groups specified in this template file are static. They do not correspond to patient records or group records within the HealthShare® demo production, because these records are procedurally generated by the demo installation script at run time.

However, you can still test the asynchronous notification feature using the group data in this demo file. To do so, replace the contact email addresses for the managing entities with active email addresses before you import the groups, and then simulate an admission event for one of the patients as described previously.

Deploy the Client Application to Test Synchronous Healthcare Action Engine Services within Unified Care Record