If you are asking how many rows would it take to hold all values in a single
table, the answer is:
2 (sex codes) * 12 (rates) * 3 (conditions) = 72
If you are thinking about using a single lookup table to replace the three
in your question, think again. That would be a really poor idea. Storing
multiple attributes in a single field is a violation of first normal form
but that's just words. You simply have no idea how annoying this structure
will be to work with.
Just the table maintenance would be a nightmare. If you added a new rate,
that would require adding 5 new rows to the table. If you added a new
condition code, that would require adding 24 new rows to the table. If you
added a new sex code (many systems use a third state to represent
"unknown"), that would require adding 36 new rows to the table. There would
be no declarative RI available to ensure that if you added a new value, you
added the correct number of instances of that value to match with the other
attributes.