FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

12.7.2 Pattern participantcontactable - Analysis

FHIR Infrastructure icon Maturity Level: 1 Informative

Detailed Cross Analysis for the participantcontactable.

12.7.2.1 Mappings

ParticipantContactable.telecom
ParticipantContactable.telecom : ContactPoint [0..*]
Resource Matches Issues Tasks Status Notes
Patient
  • Patient.telecom : ContactPoint [0..*]
    • telecom does not contain the recommended logical text for short (Pattern: A contact detail for the patient; ; Resource: A contact detail for the individual) - no reason provided telecom does not contain the recommended logical text for definition (Pattern: A contact detail (e.g. a telephone number or an email address) by which the patient may be contacted.; ; Resource: A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted.) - no reason provided telecom does not contain the recommended logical text for requirements (Pattern: Participants have (primary) ways to contact them in some way such as phone, email.; ; Resource: People have (primary) ways to contact them in some way such as phone, email.) - no reason provided
Practitioner
  • Practitioner.telecom : ContactPoint [0..*]
    • telecom does not contain the recommended logical text for definition (Pattern: A contact detail (e.g. a telephone number or an email address) by which the practitioner may be contacted.; ; Resource: A contact detail for the practitioner, e.g. a telephone number or an email address.) - no reason provided telecom does not contain the recommended logical text for requirements (Pattern: Participants have (primary) ways to contact them in some way such as phone, email.; ; Resource: Need to know how to reach a practitioner independent to any roles the practitioner may have.) - no reason provided
RelatedPerson
  • RelatedPerson.telecom : ContactPoint [0..*]
    • telecom does not contain the recommended logical text for short (Pattern: A contact detail for the related person; ; Resource: A contact detail for the person) - no reason provided telecom does not contain the recommended logical text for definition (Pattern: A contact detail (e.g. a telephone number or an email address) by which the related person may be contacted.; ; Resource: A contact detail for the person, e.g. a telephone number or an email address.) - no reason provided telecom does not contain the recommended logical text for requirements (Pattern: Participants have (primary) ways to contact them in some way such as phone, email.; ; Resource: People have (primary) ways to contact them in some way such as phone, email.) - no reason provided
ParticipantContactable.address
ParticipantContactable.address : Address [0..*]
Resource Matches Issues Tasks Status Notes
Location
  • Location.address : Address [0..1]
    • Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided address does not contain the recommended logical text for short (Pattern: An address for the location; ; Resource: Physical location) - no reason provided address does not contain the recommended logical text for definition (Pattern: An address where the location can be reached.; ; Resource: Physical location.) - no reason provided address does not contain the recommended logical text for requirements (Pattern: May need to keep track of location addresses for contacting, billing or reporting requirements and also to help with identification.; ; Resource: If locations can be visited, we need to keep track of their address.) - no reason provided
 Cardinality Problem.
Patient
  • Patient.address : Address [0..*]
    • address does not contain the recommended logical text for short (Pattern: An address for the patient; ; Resource: An address for the individual) - no reason provided address does not contain the recommended logical text for definition (Pattern: An address where the patient can be reached.; ; Resource: An address for the individual.) - no reason provided
Practitioner
  • Practitioner.address : Address [0..*]
    • address does not contain the recommended logical text for short (Pattern: An address for the practitioner; ; Resource: Address(es) of the practitioner that are not role specific (typically home address)) - no reason provided address does not contain the recommended logical text for definition (Pattern: An address where the practitioner can be reached.; ; Resource: Address(es) of the practitioner that are not role specific (typically home address). Work addresses are not typically entered in this property as they are usually role dependent.) - no reason provided address does not contain the recommended logical text for requirements (Pattern: May need to keep track of practitioner addresses for contacting, billing or reporting requirements and also to help with identification.; ; Resource: The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.) - no reason provided
RelatedPerson
  • RelatedPerson.address : Address [0..*]
    • address does not contain the recommended logical text for short (Pattern: An address for the related person; ; Resource: Address where the related person can be contacted or visited) - no reason provided address does not contain the recommended logical text for definition (Pattern: An address where the related person can be reached.; ; Resource: Address where the related person can be contacted or visited.) - no reason provided address does not contain the recommended logical text for requirements (Pattern: May need to keep track of related person addresses for contacting, billing or reporting requirements and also to help with identification.; ; Resource: Need to keep track where the related person can be contacted per postal mail or visited.) - no reason provided