Results 1 to 9 of 9

Designing a database for a cardiovascular unit

  1. #1
    raspbewwies is offline Novice
    Windows 10 Access 2016
    Join Date
    May 2019
    Posts
    1

    Designing a database for a cardiovascular unit


    Hey everyone,

    I am currently in the process of designing a simple database for basic record keeping for the service of one specialist working in a developing country - therefore owing to cost concerns and the lack of IT infrastructure, Access was deemed to be a viable starting point. However, my main wonder is whether it is possible to construct a database where updating a variable will not overrwrite its previous record. For example, if a patient has a particular plasma glucose level on one clinic visit and another on the second, is it possible to enter both in a singular table (e.g. Clinic visits)? Will this mean the creation of several hundred tables - in which case this could get quite complicated? One alternative I've thought of is the implementation of opensource EHRs (like openEMR/MRS) for the clinic visit aspect of the system and the creation of access databases to handle more static aspects of the service, like operative details, ITU stay or waiting lists for particular procedures - but the fact that this is cross platform gives me worries that I may be causing redundancy and an overly complicated system that makes more problems than it solves.

    In a nutshell, I'm looking to design a database that can be maintained easily, that links together well and can be updated with vitals without being too complicated. Thanks for any help!

  2. #2
    orange's Avatar
    orange is offline Moderator
    Windows 10 Access 2010 32bit
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    14,329
    It is difficult to advise with any focus because of the limited info.
    I think everyone on this and other database related forums would mimic your
    In a nutshell, I'm looking to design a database that can be maintained easily, that links together well and can be updated with vitals without being too complicated.
    and further with
    therefore owing to cost concerns and the lack of IT infrastructure
    .

    My only advice at this point is for you to describe the business you want to support. Start at 30,000 ft and gradually add detail. Segment the major processes/functions if necessary. You will need this info whether or not:
    -you design the database or someone else is hired to do the development, and/or
    -you choose Access or any other software for implementation.

    Good luck with your project.

  3. #3
    Dave14867's Avatar
    Dave14867 is offline Competent Performer
    Windows 10 Access 2016
    Join Date
    Nov 2016
    Location
    Upstate NY
    Posts
    278
    I would think that in very simplistic terms, a table for the patient info and another for ClinicVisit info with a foreign key in the ClinicVisit table of the PatientID would work, every time that patient visits a clinic, a new record of the visit is created. Maybe I am over simplifying it but I have used similar tables for other purposes.

    Dave

  4. #4
    Dave14867's Avatar
    Dave14867 is offline Competent Performer
    Windows 10 Access 2016
    Join Date
    Nov 2016
    Location
    Upstate NY
    Posts
    278
    See if this is what you had in mind, this is a main form for basic Patient info with a subform for each visit. Each line in the subform is a new visit instance.

    Cardio.zip

    Dave

  5. #5
    orange's Avatar
    orange is offline Moderator
    Windows 10 Access 2010 32bit
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    14,329
    Dave,

    I agree with a simple approach if in fact it is a simple business. It is the uncertainty of the poster with respect to the potential number of tables and "...like operative details, ITU stay or waiting lists for particular procedures..." that raises concern. If it is a simple record of Patient and ClinicVisit, then go for it. However, I see it as a possible project with undefined scope - sort of the artist's concept of a subdivision.
    I hope you are correct, but I can only guess what these mean to the OP
    -like operative details, ITU stay or waiting lists for particular procedures
    -plasma glucose level on one clinic visit and another on the second
    -can be updated with vitals
    -maintained easily
    -cost concerns and
    -the lack of IT infrastructure

    I am not trying to dissuade the OP. Just want to approach the reality of the situation/request with eyes-wide-open.
    The forum has a variety of participants, each with different background and experience, who are here to help/assist/advise.

  6. #6
    Dave14867's Avatar
    Dave14867 is offline Competent Performer
    Windows 10 Access 2016
    Join Date
    Nov 2016
    Location
    Upstate NY
    Posts
    278
    Orange,

    I agree with you 100% but I think I addressed his first statement or 2 about basic info, or at least the way I read it, maybe I misinterpreted what he is asking for. He then goes into the ITU, operative details etc. At least hopefully what I gave him he can use as a start and build on it from there.

    Thanks

    Dave

  7. #7
    orange's Avatar
    orange is offline Moderator
    Windows 10 Access 2010 32bit
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    14,329
    Dave,

    I agree re basic info and something as a start. We are really guessing the scope and intent until we here some feedback from the OP. Some participants are better at divining the intent and expectations of an OP than others. Some guesses amaze me --they must read between the lines (and spaces).

  8. #8
    Dave14867's Avatar
    Dave14867 is offline Competent Performer
    Windows 10 Access 2016
    Join Date
    Nov 2016
    Location
    Upstate NY
    Posts
    278
    Cleaned up a bit and entered some data so can see the results.Cardio.zip

    Dave

  9. #9
    mike60smart is offline Competent Performer
    Windows 10 Access 2016
    Join Date
    May 2018
    Location
    Living in Scotland UK
    Posts
    188
    Hi Everyone

    PMFJI but your example database is of no use whatsoever.

    VisitDate should NOT be in tblPatient - This table should only contain data related to the actual Patient and NOT the Patients Visits.

    You have created fields for each of the following :- BP, Pulse, Sugar, Temp.

    These should NOT be fields in a Table but Records in a table.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Designing a database
    By kwelch in forum Database Design
    Replies: 4
    Last Post: 10-23-2016, 11:34 AM
  2. Need help designing a database
    By Aviator in forum Database Design
    Replies: 2
    Last Post: 03-15-2016, 05:24 PM
  3. Need help designing a database
    By docpanderson in forum Programming
    Replies: 4
    Last Post: 07-01-2014, 03:03 PM
  4. Designing a database for a log
    By neo651 in forum Database Design
    Replies: 3
    Last Post: 10-31-2011, 11:45 AM
  5. Help with designing database
    By nimalp in forum Access
    Replies: 6
    Last Post: 09-15-2010, 10:34 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Tech Forums: Microsoft Office Forums