Capture Text Input

[Kev]

Hello everyone,

As my last post was a little too wordy, I thought I would simplify the
question.

How can I capture new text that a user is typing into a text box? Not
the old text plus the new text, just the new text.
I hope this is clearer?
I have left my previous explaination below if it helps explain my
objective.

Regards
Kev



I am building a patient Handover system. When a doctor ends his duty
he hands over relevant patient information to the on call doctor. My
system retrieves the relevant data out of the hospital's Clinical
information system and presents it in a more efficient format on one
screen for the doctor to view. He then enters free text into 1 to 3
text boxes (in subform datasheet view) text boxes are named

MedicalProblems
MedicalPlan
ActionsTaken

The back end sits on a SQL Server machine
Doctor can delete existing text from these controls or append new
information (full control in other words). More often than not they
just append the new information they wish to add.
I automatically insert their name and date after their entry
(afterUpdate).
During this process I also copy the control.value to another control
called Audit. Once the screen is closed I have a function that copies
the audit information from the handover table(ClinicalInstances) to an
Audit Table.

I wish to duplicate the above process except only for the appended
text in each of these controls.

The Reason:
I use the current audit table to provide a chronological "story" of
what happened to this patient.(Additional to present paper notes -
Handover information was previously wriiten on paper and then shredded
due to privacy laws - the paper was not patient centric but doctor
centric; there was no way of separating each patient's information and
storing it. Now there is.)

This however is not effective as there is so much repitition as
below:

eg Process A
27 year old woman came in with RIF pain for 4/7. WCC and CRP normal on
admission. Lapaoscopy revealed no abnormality - Renal tract US NAD.
Currently still having enoumous pain. ? Cause. - Dr Smith -
28/06/2007

27 year old woman came in with RIF pain for 4/7. WCC and CRP normal on
admission. Laparoscopy revealed no abnormality - Renal tract US NAD.
Discharge Friday - Dr Brown - 29/06/2007

What I want is this: Process B

27 year old woman came in with RIF pain for 4/7. WCC and CRP normal on
admission. Lapaoscopy revealed no abnormality - Renal tract US NAD.
Currently still having enoumous pain. ? Cause. - Dr Smith -
28/06/2007

Discharge Friday - Dr Brown - 29/06/2007 -

The reader then does not have to struggle to find the new information.

Hence I will have both processes occuring Process A for knowing
exactly what was written and what was deleted etc and Process B for
future readability.

I know there are deficiencies with this but it is still a vast
improvement on what we currently have.

I hope this explaination is clear. Is it possible to achieve this with
a Front end process or should I be looking at completeing this process
at the backend via some SQL SERVER process.

 

[Damian S]

Hi Kev,

Wouldn't the best/simplest solution to be to make each entry its own entry
rather than allowing them to append text to a free-text field. That way,
each entry could have a date, time, doctor ID and text for what they want to
say. At the end of each shift, you simply need to query your database to
return the items that have been entered for a given date/time range.

Damian.

 

[Dale Fye]

I'm with Damian,

Why would you want to allow one doctor to modify another doctors comments?
These should be separate records in a Observations data table. If you want
to merge these comments into a single text box for viewing, that is one
thing, but I would lock that textbox and force the doctor to make his new
comments in a separate record of that table. This way, you have tracability
back to the observation source. If you allow a Dr to modify someone elses
entry, then you are asking for trouble.

HTH
Dale