Results 1 to 5 of 5
  1. #1
    Join Date
    Apr 2007
    Posts
    108

    Unanswered: Current vs. Past state?

    I work in a hospital as a medical doctor. Thus no specialist in database field.

    I'm trying to design a small database that would keep track of patients that are being treated in a department and our ICU (intensive care unit). The database would also display different statistics of people being treated like breakdown by age/sex/diagnosis/operated or not. The database should also help us plan admission by showing free beds/planned discharges etc.

    One way of designing this, that I can think of is, matching resource (bed, operating room slot) vs. hospitalized patient.

    That design would easily provide above mentioned statistics for the CURRENT state of things. However I don't know how would I answer data as to: Show me the department state that was 2 weeks ago and number of operated/non-operated patients then?

    Can anyone point me in the right direction of solving these time-dependent problems?

    Thanks!

  2. #2
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    To be frank, why not employ a developer? Surely as an educated doctor, you would realise that you should be focusing on medicine, not databases. Let the developers deal with the database issues. Choose your profession.

    A man who chases two rabbits catches none.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Apr 2007
    Posts
    108
    Surely as an educated doctor, you would realise that you should be focusing on medicine, not databases.
    Maybe true in your neck of the woods.

    Where I live the reasoning and thinking-process involving wasting other people's (doctors and all others) time are greatly different.

    I'll give you some reasons why I should do it:

    1. It's my hobby, I like reading other stuff, I like reading about databases and I have personal needs for databases (not medically related).

    2. If I don't do it nobody will do it. We still use type-writers that cannot be serviced as it's unviable from a businness perspective. Getting someone to realize that good software support saves many man-hours and thus is actually a cheaper option is not possible. We have retarded leadership and we are chronically underbudgeted.

    3. I actually have diagnostic medical procedures that take less time than documenting the same procedure. The procedure takes for example 220 seconds and then I spend 300 seconds fullfiling patient form/protocol form/pathology form/cancer from etc. always filling identical data: patient name/age/security number/diagnosis. It's frustrating and getting only that (non-time dependent segment) to work would remove tremendous load of junk work and save hours (mine and other colleagues).

    4. Maybe I want to change professions - it's crappy living here being a doctor. :-)

    There are other reasons but those above top the list.

    If you are interested about locations it's:
    Zagreb, Croatia, Europe, major hospital

    We left communism a long time ago (19 years) and you can see that in how business is conducted in every other aspect of life, yet health care remains firmly burried in Karl-Marx era.

    So, while your suggestion is a good one, it's not applicable to our situation. Thank you and your input in direction of the original question would be appreciated.

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Quote Originally Posted by Riorin
    That design would easily provide above mentioned statistics for the CURRENT state of things. However I don't know how would I answer data as to: Show me the department state that was 2 weeks ago and number of operated/non-operated patients then?

    Can anyone point me in the right direction of solving these time-dependent problems?
    Presumably you have some table joining patients and resources? You would have a start and end date for these, so when a patient leaves a bed you would not delete the record but instead enter an end date. The current state of things is now found by entering the current date when querying the data, previous states by changing that date to the relevant date.

    Note that your design becomes more complex, especially in Access. For example, there is no way to force some declarative integrity constraints on time periods like this (certainly not in JET - you can fudge them in SQL Server for example) so you'll need to write lots of code to ensure that a bed is not allocated to two people in over lapping time frames.

    HTH
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,424
    Provided Answers: 8
    break it down

    patients (table)
    patientsID auto Key feild
    Fname
    sname
    DOB
    Address
    SEX

    ...
    ...
    ...

    department (table)
    departmentID auto Key feild
    Dname
    ....
    ....
    ...
    ...

    Beds (table)
    BedsID auto Key feild
    room#
    ...
    ...
    ...
    ...

    treated (table) [what type of treatment you do]
    treatedID auto Key feild
    ....
    ....
    ....
    ....



    and so on keep
    but remember to keep the Data in the Right Tables

    now link them together

    patientstoBeds (table)
    patientstoBedsID auto Key feild
    patientsID <= from the patients table
    BedsID <= from the Beds Table
    treatedID <= from the treated Table
    INDate
    OutDate
    ...
    ...
    ...
    ...


    or

    treatedtopatients (table)
    treatedtopatientsID auto Key feild
    patientsID
    treatedID
    treatedDATE
    .....
    .....
    .....
    .....

    by make a Query using the treatedtopatients you can pull in the
    sex form the patients table can do a count on the treated and


    WHAT I DO IS PUT PEN TO PAPER AND DRAW SQUARE AND PUT THE FEILD NAMES INTO EACH SQUARE THAT A TABLE AND THEN I THINK ABOUT IF FOR A COUPLE OF DAYS MAKE SHOURE YOU HAPPY WITH IT.

    Then once happy you can start the database desgining.
    hope this help

    See clear as mud


    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB based on my own environment: vb6 sp5
    ASP based on my own environment: 5.6
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    MYLE
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •