German Medical Exams

Went over GUI with MH and forced widths on table cells to make them line up more neatly, rearranged the layout of some of the data fields and tweaked border and other properties to improve GUI of results tables.

Wrote the code to figure out if any of the fields in the previous area of each record have non-default values, and if so, to display an 'expand the previous history details' area for this record.
Decided to structure each report record into 4 lines:
- always-visible fields
- patient and examiner details
- exam details
- previous history details
Modified the expand/contract controllers and added new ones so the user can:
- expand or contract the patient details for one record or for all records
- expand or contract the exam details for one record or for all records
- expand or contract the history details for one record or for all records
- expand or contract all details for one record or for all records
Those controls occupy 1/3 of the the always-visible space for each record, but I can't think of a more compact way of presenting the controls.

Also discovered a couple of instance of the dreaded "=" where it should be "==". Greg was the extra pair of eyes that helped me spot that error.

Sent MH an email asking him to review.

Start work on rewriting searchresults.inc file. Have the observations, disorders and remedies appearing in the always-there line for each record. Have the conditions, treatments and previous stuff not appearing. Still need to write the code to figure out if any of the fields in the previous area have non-default values, and if so, to display an 'expand the previous history details' area for this record, which of course entails writing the code to produce such an area, as distinct from the 'current exam details' area, and an additional control to expand them both, as well as the control to launch the editor.

Made a lot of modifications to the search.php file to accommodate changes in the fields we care about:
added variables for observation, disorder, remedy, bath, residential_care and commented out condition, treatment, facility
modified $query variable based on those changes to fields we care about
modified $left_join variable based on changes to fields we care about
modified $where variable based on changed to fields we care about
Querying appears to work successfully, reports sensible number of hits, but actual reporting is a mess until I rewrite the code which generates the results table to reflect the newly created and deleted variables.

Met with MH to go over changes we need to make in the search and report interface to reflect the changes that have been made in the database and in the add and edit record pages.

He wants in the query part a section on "patient and practioner" a section on "examination" a section on "date".
He wants in the report part a few fields to appear by default, a way to expand details on the current examination, a separate way to expand details on previous history details, and a third way to expand details on all fields.

MH asked to be able to search on a number of new fields. I looked into the implications of that (listed below) and sent him an email asking for clarification before I start changing code.
We are deprecating these fields in the database:
previous_treatment_1
previous_treatment_2
recommended_treatment_1
recommended_treatment_2
On the Search interface, there is currently a field for "Treatment" which searches all four of the treatment field in the database. Suggest we eliminate the Treatment field from the search interface.

We added a number of new fields to the database:
previous_food_rest (checkbox)
previous_exam_noted (checkbox)
previous_complex_treatment (checkbox)
previous_bath
previous_remedy
previous_residential_care
disorder_1
disorder_2
bathing
residential_care
remedy_1
remedy_2

I need MH input on
- which of these new fields to be able to search?
- what elements to add to the search interface and how do those elements relate to the fields?

To be specific:
1) able to search for those records which have the "previous_food_rest" checkbox checked or not. If so, we'd likely add an item in the search interface called "previous food rest" and which could have the values "yes", "no", "all".
2) similar question to above for the previous_exam_noted checkbox
3) similar question to above for the previous_complex_treatment checkbox

4a) "disorder_1" field in the database to be searchable?
4b) "disorder_2" field in the database to be searchable?
4c) If both, then one item in the search interface which searches them both (similar to how the treatment interface now works) or a separate item in the interface for each?

5a) "previous_bath" field in the database to be searchable?
5b) "bathing" field in the database to be searchable?
5c) If both, then one item in the search interface which searches them both (similar to how the treatment interface now works) or a separate item in the interface for each?

6) similar questions to above for "previous_residential_care" and "residential_care" fields in the database

7) similar questions to above for "previous_remedy", "remedy_1" and "remedy_2" fields in the database

Twiddled a bit with the div-based and tabled-based layouts. Will let MH look at them to see if I'm on the right path.

Created renmedical/sampleGUI/index.htm to show list of 18 records each of which consists of a text title, a small image of a page, the transcript, the translation of the transcript and a notes box. Each box is collapsible to just the text title.

I did one instance with divs and one with tables. Having a hard time getting the decorative effects (e.g. bounding rectangles) to appear properly in the div-based one because of course the two elements on the right hand side are floated so aren't considered graphically "inside" their containing object in the DOM. I've had this headache before.

Made about a dozen modifications to the edit and add pages to include additional values for a number of fields and to remove values from certain other fields.

Also investigated report that submission of record to database wasn't working, but couldn't reproduce the problem and ZS then reported everything was fine.

Added a second Remedies field in the examination section. Rewrote the code that outputs the contents of one record so that instead of one huge long line, it reports in about four shorter lines. Modified instructions posted at http://hcmc.uvic.ca/blogs/index.php?blog=39&p=5012&more=1&c=1&tb=1&pb=1