-
Type:
Change Request
-
Resolution: Unresolved
-
Priority:
Medium
-
FHIR Core (FHIR)
-
STU3
-
Financial Mgmt
-
Claim
-
Enhancement
I find it strange that the binding for Claim.type is set to 'extensible' as it forces implementers to use the five codes as-is even if they have their own set of codes for claim types. As an example, X12 defines AR - AdmissionReview which sort of maps to Institutional but doesn't give the full semantics since the AR code is specifically about admission to a facility. They also defince SC - SpecialtyCareReview for requesting a referral which maps to Professional but again doesn't give the full semantics.
Basically, unless my value set has the specific semantics of the given codes, I doubt I'll ever use them and that makes me wonder why we have this as an extensible binding and not just an example binding.
- relates to
-
FHIR-28591 Update Claim Type Definitions
-
- Resolved - change required
-
-
FHIR-27118 Update claim-type valueset to reflect industry practice
-
- Resolved - No Change
-
-
FHIR-27118 Update claim-type valueset to reflect industry practice
-
- Resolved - No Change
-