Changes applied in revision 7056

The party.organisationWorkList.expectedHospitalStay node needs to be re-instated as per http://www.openvpms.org/forum/smartflowsheet#comment-10301

Thanks for the contribution.
I've made the following changes:

• CheckInWorkFlow.CreateFlowSheetTask:

  • Changed back to subclassing AbstractTask from EditIMObjectTask, as its not editing an IMObject

  • fixed notification of task completion when displaying a FlowSheetEditDialog. It was displaying behind other dialogs.

• Removed party.organisationWorkList.expectedHospitalStay.
  The expected hospital stay can default to the appointment duration.

• Simplified ConfigurationService. Only a list of Treatment Template names is required

• NewFlowSheetTask.AddFlowSheet:

  • changed to extend AbstractTask rather than SynchronousTask. When displaying a dialog, the task is asynchronous, and must notify of completion when the dialog closes. Failure to do so means tasks execute out of order, and cancelling the dialog won't cancel the workflow.

  • now bases estimated stay on appointment length

• Removed Hospitalizations.criticalNotes. This is a field of the Patient, not the Hospitalization

• HospitalizationService now passes the visit reason name, rather than the reason code

• FlowSheetEditDialog is now modal

• removed party.organisationWorkList.customFlowSheet
  The createFlowSheet field is now a lookup with options Default and Prompt, specifying to use the defaultFlowSheetTemplate for the former, and to Prompt for the treatment template for the latter. The migration script has been updated.

Updated documentation:

• http://www.openvpms.org/documentation/csh/1.9/admin/organisation/worklist

Changes applied in revision 7026.

I have uploaded a new patch which includes retrieving the default template list and allowing for custom flow sheets to be set as they are generated.

During checkin (when the worklist has the custom flowsheet option set) or when the NewFlowSheet button is clicked a Dialog box will open populated with the current available templates and a spin box for the days you expect the patient to stay. OK will create the flowsheet with the selected options. Cancel will stop flow sheet creation as will skip in the case of the checkin workflow.

Tim I have also added a few POM build options so that when the a development build is done it builds using the SFS dev environ. Selecting the release profile will build it using the production environment. The applicationcontext has been adjusted to take these as properties from a generated smartflow.properties file.

The reason I listed the treatment template on the workflow as a default was I had defined that a worksheet could have be selected to allow for customization at admission - at that piont the edit dialog allowed for manual entry of the template name. A selection box would have been better but again I didnt want to hit the api every time we created a flow sheet... but I think thats what we need to do.