CLM_ID -- storeable as number or is it truly varchar?

20 views
Skip to first unread message

Jacob Halpert

unread,
Jul 20, 2020, 7:18:29 PM7/20/20
to Developer Group - Beneficiary Claims Data API
Hello Liani and Team,

We have noticed through extensive use of both CCLF and BB production data that the clm_id field has been consistently specified in the Information Packet and BB guidance as being of type Varchar(15), however we have yet to see any cases where the value doesn't conform to number, which would be a much more efficient way for us to store and access the field of course, vs. Varchar(15).  Do you know if we are safe to store clm_id as an integer type, or are there any edge cases that we should be aware of that require us to leave the field as Varchar(15)?

Best,

Jake

Karl Davis

unread,
Jul 21, 2020, 10:03:23 AM7/21/20
to Developer Group - Beneficiary Claims Data API
Jacob,

Our upstream data sources report to us that it's a string, so -- even though all the data we currently have is numeric (I think -- been a while since I've checked) -- we cannot make any guarantees that that will always remain the case. I'd leave as text in your DB, if I were you.

Best regards,
Karl M. Davis, BCDA, etc. team
Reply all
Reply to author
Forward
Message has been deleted
0 new messages