AnsweredAssumed Answered

Handling a bazillion fields

Question asked by dsimonson on Oct 25, 2014
Latest reply on Oct 26, 2014 by philmodjunk


Handling a bazillion fields


In the anesthesia clinical record/billing solution I am working on, I am creating a ton of fields.  Most are tied to a specific surgery, so I am creating them in the SURGERIES table.  However, even though they will be unique to a single surgery and so (to my understanding) can reasonably all be added to that table, I find that the number is getting very large. 


I was thinking that I could split them off into separate tables, tied to the SURGERIES record by a key field.  Thus, I could create a table called "CMS_FIELDS" that would have all of the fields related to completing the CMS claim form for the surgery, and another table called "CLINICAL RECORD" that would have all of the fields related to the clinical record for that surgery.  

My question is:  is that the best way to do it?  Thanks.


Dan Simonson, CRNA, MHPA
2607 S. Manito Blvd.
Spokane, WA 99203

H. (509) 747-0819
C. (509) 981-6274