Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. blood Pressure

blood Pressure

Scheduled Pinned Locked Moved Database
questiondatabasehelp
5 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    Jassim Rahma
    wrote on last edited by
    #1

    I have a medical software and I want to know what's the best control to use and what's the best SQL field type for blood pressure? The blood pressure as you know is in this format: 999/999 it also has a flag for either right hand (L) or left hand (R), something like radio control I don't want the traditional way!! I mean two numeric and two radio?! I thought of the ButtonEdit from DevExpress with a ###/### mask but I faced a problem with the L and R flags.. What is your advise?

    N I T 3 Replies Last reply
    0
    • J Jassim Rahma

      I have a medical software and I want to know what's the best control to use and what's the best SQL field type for blood pressure? The blood pressure as you know is in this format: 999/999 it also has a flag for either right hand (L) or left hand (R), something like radio control I don't want the traditional way!! I mean two numeric and two radio?! I thought of the ButtonEdit from DevExpress with a ###/### mask but I faced a problem with the L and R flags.. What is your advise?

      N Offline
      N Offline
      Not Active
      wrote on last edited by
      #2

      This is not a database question. WHy are you spamming the fourms :mad:


      I know the language. I've read a book. - _Madmatt

      1 Reply Last reply
      0
      • J Jassim Rahma

        I have a medical software and I want to know what's the best control to use and what's the best SQL field type for blood pressure? The blood pressure as you know is in this format: 999/999 it also has a flag for either right hand (L) or left hand (R), something like radio control I don't want the traditional way!! I mean two numeric and two radio?! I thought of the ButtonEdit from DevExpress with a ###/### mask but I faced a problem with the L and R flags.. What is your advise?

        I Offline
        I Offline
        i j russell
        wrote on last edited by
        #3

        Maybe you could have split the question into two and posted the db related part here? How about creating a new table for storing the historical data (ReadingDate DATE, Side BIT, UpperReading INT, LowerReading INT). By doing this, you will have a history of readings as well as the current one. Ian

        1 Reply Last reply
        0
        • J Jassim Rahma

          I have a medical software and I want to know what's the best control to use and what's the best SQL field type for blood pressure? The blood pressure as you know is in this format: 999/999 it also has a flag for either right hand (L) or left hand (R), something like radio control I don't want the traditional way!! I mean two numeric and two radio?! I thought of the ButtonEdit from DevExpress with a ###/### mask but I faced a problem with the L and R flags.. What is your advise?

          T Offline
          T Offline
          T M Gray
          wrote on last edited by
          #4

          My advice is never store multiple pieces of data in one column unless you absolutely can't avoid it. Systolic pressure and diastolic pressure are distinct pieces of data and should be recorded separately. Do you have a valid reason for avoiding the "traditional" way? To show you why they should be stored separately here is part of a blood donation form. "Donors must have blood pressure values of 180 or less for the top (systolic) number and 100 or less for the bottom (diastolic) number. Donors with values greater than 140/90 may wish to consult their personal physician." So as you can see, the numbers for eligibility are different than the numbers where you should be concerned. Not only that, but the difference between the concern and max numbers is different for the two pieces of data. So if anyone ever wanted a report where the pressure was above the rate of concern, but below the maximum for donation that query would be much more difficult to write if you combined the data. You also couldn't do proper sorting.

          J 1 Reply Last reply
          0
          • T T M Gray

            My advice is never store multiple pieces of data in one column unless you absolutely can't avoid it. Systolic pressure and diastolic pressure are distinct pieces of data and should be recorded separately. Do you have a valid reason for avoiding the "traditional" way? To show you why they should be stored separately here is part of a blood donation form. "Donors must have blood pressure values of 180 or less for the top (systolic) number and 100 or less for the bottom (diastolic) number. Donors with values greater than 140/90 may wish to consult their personal physician." So as you can see, the numbers for eligibility are different than the numbers where you should be concerned. Not only that, but the difference between the concern and max numbers is different for the two pieces of data. So if anyone ever wanted a report where the pressure was above the rate of concern, but below the maximum for donation that query would be much more difficult to write if you combined the data. You also couldn't do proper sorting.

            J Offline
            J Offline
            Jassim Rahma
            wrote on last edited by
            #5

            well, i won't have issue saving it separately in the sql server but I don't want many controls on the form? so what's the best way to have some thing like a mask of 999/999 Left or 999/999 Right?

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups