Danish MedCom Core
2.1.0 - Release DK

This page is part of the DK MedCom Core (v2.1.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Data Type Profile: MedComMessagingContactPoint

Official URL: http://medcomfhir.dk/ig/core/StructureDefinition/medcom-messaging-contactpoint Version: 2.1.0
Active as of 2022-11-24 Computable Name: MedComMessagingContactPoint

The datatype ContactPoint is specified for use in MedCom messages.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from ContactPoint

NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint 0..*ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... system S0..1codephone | fax | email | pager | url | sms | other
... value S0..1stringThe actual contact point details
... use S0..1codehome | work | temp | old | mobile - purpose of this contact point

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint C0..*ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... system SΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required): Telecommunications form for contact point.

... value SΣ0..1stringThe actual contact point details
... use ?!SΣ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required): Use of contact point.


doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
ContactPoint.systemrequiredContactPointSystem
ContactPoint.userequiredContactPointUse

Constraints

IdGradePath(s)DetailsRequirements
cpt-2errorContactPointA system is required if a value is provided.
: value.empty() or system.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint C0..*ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... id 0..1stringUnique id for inter-element referencing
... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
... system SΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required): Telecommunications form for contact point.

... use ?!SΣ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required): Use of contact point.

... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
... period Σ0..1PeriodTime period when the contact point was/is in use

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
ContactPoint.systemrequiredContactPointSystem
ContactPoint.userequiredContactPointUse

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

This structure is derived from ContactPoint

Summary

Must-Support: 3 elements

Differential View

This structure is derived from ContactPoint

NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint 0..*ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... system S0..1codephone | fax | email | pager | url | sms | other
... value S0..1stringThe actual contact point details
... use S0..1codehome | work | temp | old | mobile - purpose of this contact point

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint C0..*ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... system SΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required): Telecommunications form for contact point.

... value SΣ0..1stringThe actual contact point details
... use ?!SΣ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required): Use of contact point.


doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
ContactPoint.systemrequiredContactPointSystem
ContactPoint.userequiredContactPointUse

Constraints

IdGradePath(s)DetailsRequirements
cpt-2errorContactPointA system is required if a value is provided.
: value.empty() or system.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. ContactPoint C0..*ContactPointDetails of a Technology mediated contact point (phone, fax, email, etc.)
... id 0..1stringUnique id for inter-element referencing
... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
... system SΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required): Telecommunications form for contact point.

... use ?!SΣ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required): Use of contact point.

... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
... period Σ0..1PeriodTime period when the contact point was/is in use

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
ContactPoint.systemrequiredContactPointSystem
ContactPoint.userequiredContactPointUse

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

This structure is derived from ContactPoint

Summary

Must-Support: 3 elements

 

Other representations of profile: CSV, Excel, Schematron