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

HealtcareService & Practitioner does not support a contact with specific purpose

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • HealthcareService
      Practitioner
    • Hide

      In HealthcareService, PractitionerRole and OrganizationAffilitiation add a new backbone element structure:

      contact 0..
      purpose 0..1 CodeableConcept (purpose of this contact)
      name 0..1 HumanName/string? (name associated with contact)
      telecom 0..       ContactPoint
      address 0..* Address (addresses applicable to the purpose e.g. Accounts payable, Legal enquiries, etc - not service addresses, these are at locations)

      Guidance will be added to the telecom definition to indicate that if there is a specific purpose for the telecom, this should be captured in the contact backbone element.

      Show
      In HealthcareService, PractitionerRole and OrganizationAffilitiation add a new backbone element structure: contact 0.. purpose 0..1 CodeableConcept (purpose of this contact) name 0..1 HumanName/string? (name associated with contact) telecom 0.. ContactPoint address 0..* Address (addresses applicable to the purpose e.g. Accounts payable, Legal enquiries, etc - not service addresses, these are at locations) Guidance will be added to the telecom definition to indicate that if there is a specific purpose for the telecom, this should be captured in the contact backbone element.
    • Brian Postlethwaite/Alex de Leon: 4-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      In most scenarious it is required to define the purpose of a contact point (telephone, email, etc) such as Emergency Number, After Hours.

      Within the Organisation resource, the attribute Organisation.contact was introduced to support this requirement. However this is not possible within FHIR 3.0.1 at this time within HealthcareService & Practitioner.

      The recommendation is to apply the same concept for "contact purpose" as defined in Organisation to HealthcareService & Practitioner.

      eg. HealthcareService.contact & Practitioner.contact.

      This approach would align the mechanism to define contacts with specific purposes across most FHIR Resources.

      Another approach would be to add support for "purpose" (not the "use") to "ContactPoint" & "Address".

      eg. ContactPoint.purpose & Address.purpose

      Attachments

        1. healthcareservice.json
          0.6 kB
        2. PractitionerRole01.json
          0.7 kB

        Activity

          People

            brian.postlethwaite Brian Postlethwaite
            jaco.olivier Jaco Olivier
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: