Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

R4
Work Group:

Patient Administration
Related Artifact(s):

HealthcareService
Resolution Description:

Hide

The EOB.supportingInfo is so generic it can't really be used for anything interopreable. Having extensions for that content seems desirable, as you can have an extension URL that provides the meaning of the thing. We'd recommend using extensions in HealthcareService so you can be more targeted about the meaning of the related data.

Also, HealthcareService.extraDetails is just a texual field for viewing in a directory. Any "supporting info" data would be in another spot (e.g., an extension or characteristic).

Show
The EOB.supportingInfo is so generic it can't really be used for anything interopreable. Having extensions for that content seems desirable, as you can have an extension URL that provides the meaning of the thing. We'd recommend using extensions in HealthcareService so you can be more targeted about the meaning of the related data. Also, HealthcareService.extraDetails is just a texual field for viewing in a directory. Any "supporting info" data would be in another spot (e.g., an extension or characteristic).
Change Category:
Clarification

Recommend changing extraDetails to be defined identically (after Jira#25444) as EOB.supportingInfo.

The supportingInfor design is much more useful that extraDetails in its current design. Plus, this would be more consistent for implementers.