Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIR Core (FHIR)
-
R5
-
Modeling & Methodology
-
Datatypes
-
-
Cooper Thompson / Brian Postlethwaite : 7-0-0
-
Enhancement
-
Compatible, substantive
-
R5
Description
PA has had several use case for a role-specific contact. For example, Organization.contact. This include an address, telecom, HumanName, and role. There has also been discussion about adding a period to represent the effective time range for the contact, but that has been more controversial.
We wanted to propose making a data type that could represent this without duplicating a backbone element. Alternatively we could expand ContactPoint, but that seems more disruptive.
BR&R expressed interest in being involved in discussions about this data type (specifically, Petere Bomberg)
Attachments
Issue Links
- relates to
-
FHIR-25375 Location lacks a Contact
- Published
-
FHIR-29034 Remove Organization.telecom and address
- Published
-
FHIR-25377 Additional concepts needed in the contact-point-use and address-us value sets
- Resolved - No Change
-
FHIR-33097 Addition of values in address-use value set
- Resolved - No Change
-
FHIR-31542 Add Relationship Type Extension to Patient.contact
- Duplicate
-
FHIR-27005 Period missing from Contact
- Published
-
FHIR-35835 Allow the iso21090-preferred extension as allowed for new ExtendedContactDetail
- Published
-
FHIR-37650 Updated ExtendedContactDetail to allow 0..* names
- Published
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...