Stream: terminology
Topic: Multiple codes for concepts, instance edition
Jay Lyle (Apr 06 2021 at 10:58):
In our legacy Coverage file, there are 4 different fields for subscriber relationship to patient (original, hipaa, ncpdp (2)). I think we can call these different representations of a single relationship, so we can populate the 0..1 CodeableConcept with 4 Codings with different systems. Right?
Lloyd McKenzie (Apr 06 2021 at 16:25):
If they're all representing the same relationship, that's fine.
Robert McClure (Apr 08 2021 at 23:54):
@Jay Lyle I think you should provide an example or two. I'm struggling to imagine a situation where some sort of concept from each of those areas (original, hippa, NCPDP, NCPDP) can all represent the same idea.
Jay Lyle (Apr 09 2021 at 14:10):
Sure:
File FileName Field FieldName Code Label
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 01 SPOUSE
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 18 SELF
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 19 CHILD
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 20 EMPLOYEE
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 29 SIGNIFICANT OTHER
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 32 MOTHER
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 33 FATHER
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 39 ORGAN DONOR
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 41 INJURED PLAINTIFF
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA 53 LIFE PARTNER
2.312 INSURANCE TYPE 4.03 PT. RELATIONSHIP - HIPAA G8 OTHER RELATIONSHIP
2.312 INSURANCE TYPE 4.05 PHARMACY RELATIONSHIP CODE 0 NOT SPECIFIED
2.312 INSURANCE TYPE 4.05 PHARMACY RELATIONSHIP CODE 1 CARDHOLDER
2.312 INSURANCE TYPE 4.05 PHARMACY RELATIONSHIP CODE 2 SPOUSE
2.312 INSURANCE TYPE 4.05 PHARMACY RELATIONSHIP CODE 3 CHILD
2.312 INSURANCE TYPE 4.05 PHARMACY RELATIONSHIP CODE 4 OTHER
2.312 INSURANCE TYPE 6 WHOSE INSURANCE v Veteran
2.312 INSURANCE TYPE 6 WHOSE INSURANCE s Spouse
2.312 INSURANCE TYPE 6 WHOSE INSURANCE o Other
Robert McClure (Apr 09 2021 at 14:52):
Ok - so I think what you are saying is as an example, that relationship element for a single instance might have HIPAA 01, NCPDP 1, original s. If so then I agree with Lloyd, you can put all three in that example into one codableconcept. You'll need to define a code system for each and keep in mind that these are all external code systems so if a standards IG you need to get HTA to represent the metadata. And we'll need to clarify the IP for NCPDP. I'd guess HIPAA is actually VA-HIPPA?
Last updated: Apr 12 2022 at 19:14 UTC
