Sample Clinical Pathway
A ClinicalPathway? is a definition of the process and variables that are used by that process as well as other aspects like billing.
The process is jPDL (Jboss Process Definition Language), the variables is a custom format.
A process like:
Description of the steps
Intake step
This step functionally does the following: - make an appointment with the patient - have a small medical form (change the sample form to support this sample process) inserted with intake results (should proceed yes/no) - have the appointment signed off after happening
Based on entry of the decision in the healthrecord, a event is should be thrown and catched to continue this flow to the next step
The whole bundle uses Spring DM to register it's service (pathway) and needs a way to register (event listeners?) it's interest in CRUD operations on the healthRecord
Descision if grouptherapie is possible
Based on the intake form (should proceed yes/no) automatically continue the process at the right track (need to figure out how to actually do this with jPDL)
Doorverwijzen
Create a simple email and send it to the patient and the referrer of the patient (no therapy adviced, please consult your GP)
Groupstherapy
This step consists of the following actions:
- have a patient enroll in a group (create a group, create the appointments for the group)
- monitor if when the last appointment is 'done' using the Appointment Done Event (this needs a proper name and is not in the system yet)
- continue the process after this last appointment.
NOTE: at this moment, the process does not create the group and appoinments, this is done using a supporting system (web based / calendar based) and needs to be created (partly)
Ontslag
This is a step to formally 'dismiss' the patient, treatment is done.
* have a letter of 'dismissal' created and send to the patient and referrer.
The Definition
gives a pathway definition of
<cpw:clinicalpathway cpw="http://joiningtracks.org/clinicalpathway/1.0">
<cpw:name>Sample Clinical Pathway</cpw:name>
<!-- there is no need to specifiy the type (jpdl) other flow support will change the version of the pathway flow -->
<cpw:process>bundle:jpdl/processdefinition.xml</cpw:process>
<cpw:variables>
<!-- key value types over here : for instance
- number of meetings in 'groepstherapie' -->
<!-- use a standard way of xml key value definition mechanism (like properties)
these are available in the process actions to use -->
</cpw:variables>
<cpw:contract>
<cpw:party type="insurance">
<cpw:costcodes> <!-- here the DBC (for dutch) combination for invoicing -->
<cpw:costcode type="DBC">A31.3</cpw:costcode>
<cpw:amount>1200.00</cpw:amount>
</cpw:costcodes>
</cpw:party>
<cpw:party type="patient">
</cpw:party>
</cpw:contract>
</cpw:clinicalpathway>
NOTES
- THE XML is not valid (yet), the whole concept is at is start phase and is SUBJECT TO CHANGE
- A reference to the jPDL may be better as the whole clinical pathway is delivered as a bundle that should contain the jPDL (and other things) (already changed)
- The variables (and maybe contract details) need to become part of the execution of the flow (somehow)
This sample is updated to match the progress on the subject.
Attachments
- sample-pathway.png (25.7 kB) -
Sample Clinical Pathway
, added by olger on 05/22/08 20:57:24.

