Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5970593
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T20:23:51+00:00 2026-05-22T20:23:51+00:00

I am programming a database. I have one requirement, I am unsure how to

  • 0

I am programming a database. I have one requirement, I am unsure how to implement it.The database is about medical related information. It is as follows:

  1. Ventricular Arrangement: This begins as a single entry box that becomes 7 separate fields to describe the ventricles:

    a. Number of Ventricles (Vent_No): 2 choices = 1 or 2.

    i. If choice is 1 then this field needs to be filled:
    1. Ventricular Morphology (UniVent_Morph): 3 choices = Right, Left, Indeterminate (for >>this field, we may have to have a popup box that explains that this does not apply to >>situations where there is a ‘hypoplatic’ ventricle. Examples of this situation include >>unbalanced AVSD, HLHS, PAA with IVS, etc. These hearts would be coded using the 2 >>ventricle drop down list).
    ii. If choice is 2 then this drop-down occurs with 4 fields to fill:

    1. Right Sided Ventricular Morphology (RitS_Vent_Morph): 3 choices = Right, Left, >>>Indeterminate.
    2. Right Sided Ventricular Size (RitS_Vent_Size): 3 choices = Normal, Hypoplastic, >>>Enlarged.
    3. Left Sided Ventricular Morphology (LftS_Vent_Morph): 3 choices = Right, Left, Indeterminate.
    4. Left Sided Ventricular Size (LftS_Vent_Size): 3 choices = Normal, Hypoplastic, >>>Enlarged.

    b. For the complex ventricular malformations, we need to have a ‘memo’ field pop up for description (this may be in a separate table linked by the SpcUI field).

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T20:23:51+00:00Added an answer on May 22, 2026 at 8:23 pm

    I would probably do something like this:

    Ventricles
    PatientId int (not null)
    VentricularMorphologyTypeid (int not null) 
    VentricularMorphologyid (int not null)
    VentricularSizeID (int null)
    Notes (nvarchar(max) null)
    

    Then I would create three lookup tables for the potential values for the typeId (1 or 2 and descriptons as to what 1 and 2 are (UniVent_Morph and ?) and for the Morphology Id (Right Left and indeterminate) and for the Ventricular size ( Normal, Hypoplastic, Enlarged). I would create foreign key constraints to the lookup tables and the patient table so that only those values can be recorded.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This is a general database question, not related to any particular database or programming
LINQ simplifies database programming no doubt, but does it have a downside? Inline SQL
I usually do web programming but have a requirement for a windows form in
So, I've had a fair amount of experience programming database driven web apps using
I create business applications with heavy database use. Most of the programming work is
I'm fairly new to database programming in .NET. If I want to call several
I am new to database programming with Google App Engine and am programming in
I'm a bit new to database programming in general, and even newer to Entity
I am learning on my own about writing an interpreter for a programming language,
i used v s 2010 i have one problem..when i delete more then one

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.