Generated Narrative: StructureDefinition DIPSPerson Name Flags Card. Type Description & Constraints Person 0..* NoBasisPerson A generic person record #xD; meta #xD; Slices for security 0..* Coding Security Labels applied to this resource Slice: Unordered, Open by exists:system #xD; security:addressConfidentiality 0..* Coding Security Labels applied to this resource #xD; system 0..1 uri Identity of the terminology system Fixed Value: http://ehelse.no/fhir/CodeSystem/gd-address-confidentiality #xD; code 0..1 code graderingsnivå from FREG #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:language 0..1 (Complex) Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonLanguage #xD; value[x] #xD; system 0..1 uri Identity of the terminology system Fixed Value: urn:oid:1.3.6.1.4.1.9038.52.1587 #xD; version 0..0 Version of the system - if relevant #xD; userSelected 0..0 If this coding was chosen directly by the user #xD; extension:deathRegisteredTime 0..1 dateTime Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonDeathRegisteredTime #xD; extension:deathComment 0..1 string Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonDeathComment #xD; extension:deathRegisteredBy 0..* string Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonDeathRegisteredBy #xD; extension:hospitalSectorId 0..1 id Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonHospitalSectorId #xD; extension:hospitalSectorName 0..* string Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonHospitalSectorName #xD; identifier 1..* Identifier A human identifier for this person #xD; type 0..0 Description of identifier #xD; value 0..1 string The value that is unique #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; Slices for identifier Content/Rules for all slices #xD; identifier:FNR 0..* Identifier Norwegian FNR #xD; type 0..0 Description of identifier #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; identifier:DNR 0..* Identifier The D-nummer of the patient #xD; type 0..0 Description of identifier #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; identifier:PersonID 1..1 Identifier A human identifier for this person #xD; use 0..0 usual | official | temp | secondary | old (If known) #xD; system 1..1 uri The namespace for the identifier value Fixed Value: http://dips.no/fhir/namingsystem/dips-personid #xD; value 1..1 string The value that is unique #xD; name #xD; id 0..0 Unique id for inter-element referencing #xD; use 0..0 usual | official | temp | nickname | anonymous | old | maiden #xD; prefix 0..0 Prefix is not used in Norwegian names #xD; suffix 0..0 Suffix is not used in Norwegian human names #xD; period 0..0 Time period when name was/is in use #xD; address #xD; id 0..1 string Unique id for inter-element referencing #xD; Slices for extension Content/Rules for all slices #xD; extension:official 0..* NoBasisAddressOfficial The concept of an officially registered address #xD; extension:stateName 0..1 string Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonStateName #xD; extension:lastOfficialAddressSyncTime 0..1 dateTime Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonLastOfficialAddressSyncTime #xD; <a href="StructureDefinition-DIPSPerson-definitions.html#Person.address.use" title="The purpose of this address.#xD;#xA;#xD;#xA;Mapping of values to other Norwegian CodeSystems is documented in the implementation guide. In general the address used for visiting the person should have use "home" and type "physical" or "both". The "official" flag can be either true or false.#xD;#xA;#xD;#xA;derive from database column -- dipscoredb.dwadresse.dipscadresse and dipscoredb.dwkodeverkverdier.Kode">use 0..1 code home | work | temp | old | billing - purpose of this address #xD; line 0..* string Street name, number, direction & P.O. Box etc. #xD; city 0..1 string Poststed or city #xD; district 0..1 string name of "kommune" #xD; Slices for extension Content/Rules for all slices #xD; extension:muniplaity 0..1 (Complex) Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/DIPSPersonMunicipality #xD; value[x] #xD; system 0..1 uri Identity of the terminology system Fixed Value: urn:oid:2.16.578.1.12.4.1.1.3402 #xD; version 0..0 Version of the system - if relevant #xD; userSelected 0..0 If this coding was chosen directly by the user #xD; <a href="StructureDefinition-DIPSPerson-definitions.html#Person.address.state" title="Name of the norwegian "fylke"). If fylkes-number is required "eiendomsinformasjon" should be used with koded kommune-number.#xD;#xA;#xD;#xA;Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes).#xD;#xA;#xD;#xA;#xD;#xA;database column -- dipscoredb.dwkodeverkverdier.kode">state 0..1 string norwegian "fylke" #xD; postalCode 0..1 string Postal code for area #xD; country 0..1 string Country (e.g. can be ISO 3166 2 or 3 letter code) #xD; period #xD; start 0..1 dateTime Starting time with inclusive boundary #xD; photo 0..0 Image of the person #xD; managingOrganization 0..0 The organization that is the custodian of the person record #xD; link 1..1 BackboneElement Link to a resource that concerns the same actual person #xD; Documentation for this format
Demographics and administrative information about a person independent of a specific health-related context.
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). database column - - dipscoredb.dwperson.personid
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Person(classCode="PSN" and determinerCode="INST" and quantity="1")
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
When the resource last changed - e.g. when the version changed.
This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http://hl7.org/fhir/R4/http.html#read) interaction.
Identifies where the resource comes from
A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](http://hl7.org/fhir/R4/provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.
In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
Profiles this resource claims to conform to
A list of profiles (references to [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](http://hl7.org/fhir/R4/structuredefinition-definitions.html#StructureDefinition.url).
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Security Labels applied to this resource
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Security Labels from the Healthcare Privacy and Security Classification System.
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
nivå av beskyttelsesgrad på informasjon Gyldige kodeverdier er: • ugradert • fortrolig • strengtFortrolig (strengt fortrolig)
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Optional Extension Element - found in all resources.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Source of the definition for the extension code - a logical name or a URL.
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.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
An identifier for this person. Should be at Fødselsnummer or D-nummer Identifier for a person within a particular scope.
People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the person. Examples are national person identifier and local identifier.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Fødselsnummer for the patient. Fødselsnummer as one of the possible patient identifier, should at least be sent unless there is a reason not to. Reasons for not sending the Fødselsnummer include but are not limited to, research and apps without a contract for processing data. Multiple FNR can exist for a person. If several FNR is provided the time period that each identifier is valid should be provided. No information about period is required when only one FNR is provided.
Identifies that this is a Norwegian Fødselsnummer
The D-nummer of the patient. (assigned by the norwegian Skatteetaten)
The identification of the Norwegian D-nummer
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
Person may have multiple names with different uses or applicable periods.
Need to be able to track the person by multiple names. Examples are your official name and a partner name.
Defines a middle name as a specific extension as this is widely used in Norwegian names. The middlename is defined in norwegian legislation (lov om personnavn).
usual | official | temp | nickname | anonymous | old | maiden
Applications can assume that a name is current unless it explicitly says that it is temporary or old.
Allows the appropriate name for a particular context of use to be selected from among a set of names.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old name etc.for a current/permanent one
XPN.7, but often indicated by which field contains the name
Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.
Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
Ref. "lov om personnavn" for further details about Norwegian HumanNames. The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father.
Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).
Given name. In Norway Given name does not include middlenames according to the regulation for norwegian names. Multiple given names are however legal. Ref. "Lov om personnavn" for further details about Norwegian HumanNames.
If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.
Given Names appear in the correct order for presenting the name
This is not a part of official Norwegian names as defined in "lov om personnavn" regulation. Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.
Prefixes appear in the correct order for presenting the name
Suffix is not used in Norwegian human names
This is not a part of official Norwegian names as defined in "lov om personnavn" regulation. Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.
Suffixes appear in the correct order for presenting the name
Indicates the period of time when this name was valid for the named person.
Allows names to be placed in historical context.
A contact detail for the person, e.g. a telephone number or an email address.
Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification.
People have (primary) ways to contact them in some way such as phone, email.
The gender might not match the biological sex as determined by genetics, or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than M and F, though a clear majority of systems and contexts only support M and F.
Needed for identification of the person, in combination with (at least) name and birth date. Gender of person drives many clinical processes.
The gender of a person used for administrative purposes.
player[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
At least an estimated year should be provided as a guess if the real DOB is unknown.
Age of person drives many clinical processes, and is often used in performing identification of the person. Times are not included so as to not confuse things with potential timezone issues.
Person may have multiple addresses with different uses or applicable periods.
May need to keep track of person's addresses for contacting, billing or reporting requirements and also to help with identification.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. database column -- dipscoredb.dwadresse.adresseid
The concept of an officially registered address
Defines the concept of an officially registered address in Norway. Usually this will be the adress registered in "Folkeregisteret" for persons or "Enhetsregisteret" for organizations. database column -- dipscoredb.dwperson.fregoppdatering
The name and number of the of the urban district of this address.
Identification of a real property in Norway is defined using gårdsnummer, bruksnummer and kommunenummer. In addition real property can be rented out, the area of the real property that is rented is measured and is further identified by its festenummer. In addition some real property is split into sections identified by its seksjonsnummer
home | work | temp | old | billing - purpose of this address
The purpose of this address. Mapping of values to other Norwegian CodeSystems is documented in the implementation guide. In general the address used for visiting the person should have use "home" and type "physical" or "both". The "official" flag can be either true or false. derive from database column -- dipscoredb.dwadresse.dipscadresse and dipscoredb.dwkodeverkverdier.Kode
Applications can assume that an address is current unless it explicitly says that it is temporary or old.
Allows an appropriate address to be chosen from a list of many.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. Mapping of values to other Norwegian CodeSystems is documented in the implementation guide. In general the address used for visiting the person should have use "home" and type "physical" or "both". The "official" flag can be either true or false.
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the [Location](http://hl7.org/fhir/R4/location.html#) resource).
The type of an address (physical / postal).
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
XAD.1 + XAD.2 + XAD.3 + XAD.4 + XAD.5 + XAD.6
Street name, number, direction & P.O. Box etc.
This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information. database column -- dipscoredb.dwadresse.dipscadresse
The order in which lines should appear in an address label
XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)
When a postalcode is given the name of the city must be according to the official list of postalcodes used in Norway. The name of the city, town, village or other community or delivery center. database column -- dipscoredb.dwkodeverkverdier.langtnavn
Name of the county (norwegian "kommune"). If kommune number is required "eiendomsinformasjon" should be used. The name of the administrative area (county). database column -- dipscoredb.dwkodeverkverdier.langtnavn
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
unique id for the element within a resource (for internal references)
Coded value for municipality/county Norwegian kommune
Name of the norwegian "fylke"). If fylkes-number is required "eiendomsinformasjon" should be used with koded kommune-number. Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes). database column -- dipscoredb.dwkodeverkverdier.kode
A postal code designating a region defined by the postal service. In Norway this is af four digit number defined by the norwegian postal service. database column -- dipscoredb.dwkodeverkverdier.Kode
Country (e.g. can be ISO 3166 2 or 3 letter code)
Country - a nation as commonly understood or generally accepted. database column -- dipscoredb.dwkodeverkverdier.langtnavn
ISO 3166 3 letter codes can be used in place of a human readable country name.
Allows addresses to be placed in historical context.
The start of the period. The boundary is inclusive. database column -- dipscoredb.dwadresse.Gyldigfradato
If the low element is missing, the meaning is that the low boundary is not known.
End time with inclusive boundary, if not ongoing
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing
An image that can be displayed as a thumbnail of the person to enhance the identification of the individual.
player[classCode=PSN|ANM and determinerCode=INSTANCE]/desc
The organization that is the custodian of the person record
The organization that is the custodian of the person record.
Need to know who recognizes this person record, manages and updates it.
Whether this person's record is in active use.
Need to be able to mark a person record as not to be used because it was created in error.
This element is labelled as a modifier because it is a status element that can indicate that a record should not be treated as valid
Link to a resource that concerns the same actual person
Link to a resource that concerns the same actual person.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The resource to which this actual person is associated
The resource to which this actual person is associated.
Level of assurance that this link is associated with the target resource.
The level of confidence that this link represents the same actual person, based on NIST Authentication Levels.