- HSPC Implementation Guide

This page is part of the HSPC FHIR Implementation Guide (v0.1.0: Daft For Comment Draft) based on FHIR v1.9.0. This is the current published version. For a full list of available versions, see the Directory of published versions

individualPerson

Source: XML, JSON, Turtle

Differential

NameFlagsCard.TypeDescription & Constraintsdoco
.. Extension 0..1
... url 1..1uri"http://fhir.org/guides/hspc/StructureDefinition/hspc-provenance-attribution-individualPerson"
... value[x] 0..1Reference(Person)

doco Documentation for this format

Snapshot

NameFlagsCard.TypeDescription & Constraintsdoco
.. Extension I0..1Extension
ext-1: Must have either extensions or value[x], not both
... id 0..1stringxml:id (or equivalent in JSON)
... extension 0..*ExtensionAdditional Content defined by implementations
... url 1..1uri"http://fhir.org/guides/hspc/StructureDefinition/hspc-provenance-attribution-individualPerson"
... valueReference 0..1Reference(Person)A generic person record

doco Documentation for this format

Definitions

Extension(individualPerson)
Definition

IndividualPerson is the identifying information that describes an individual: name, ID.

Control0..1
InvariantsDefined on this element
ext-1: Must have either extensions or value[x], not both (xpath: exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')]))
Extension.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
Extension.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Extension.url
Definition

Source of the definition for the extension code - a logical name or a URL.

Control1..1
Typeuri
Comments

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Fixed Valuehttp://fhir.org/guides/hspc/StructureDefinition/hspc-provenance-attribution-individualPerson
Extension.valueReference
Definition

Demographics and administrative information about a person independent of a specific health-related context.

Control0..1
TypeReference(Person)
Comments

The Person resource does justice to person registries that keep track of persons regardless of their role. The Person resource is also a primary resource to point to for people acting in a particular role such as SubjectofCare, Practitioner, and Agent. Very few attributes are specific to any role and so Person is kept lean. Most attributes are expected to be tied to the role the Person plays rather than the Person himself. Examples of that are Guardian (SubjectofCare), ContactParty (SubjectOfCare, Practitioner), and multipleBirthInd (SubjectofCare).