Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-29035

Create (or update) a data type for representing a comprehensive "Contact"

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Modeling & Methodology
    • Datatypes
    • Hide

      We will create a new data type as indicated below. Updating other resources to refer to this new data type will be handled in other trackers.

      ExtendedContactDetail Element

      purpose 0..1 CodeableConcept The type of contactEntityType (Preferred)

      name 0..1 HumanName A name associated with the contact

      telecom 0..* ContactPoint Contact details (telephone, email, etc.) for a contact

      address 0..1 Address Visiting or postal addresses for the contact

      organization I 0..1 Reference(Organization)

      period 0..1 Period

      Show
      We will create a new data type as indicated below. Updating other resources to refer to this new data type will be handled in other trackers. ExtendedContactDetail Element purpose 0..1 CodeableConcept The type of  contactEntityType (Preferred) name 0..1 HumanName A name associated with the contact telecom 0..* ContactPoint Contact details (telephone, email, etc.) for a contact address 0..1 Address Visiting or postal addresses for the contact organization I 0..1 Reference(Organization) period 0..1 Period
    • 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

        Activity

          People

            brian.postlethwaite Brian Postlethwaite
            cooper.thompson Cooper Thompson
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: