Generated Narrative: StructureDefinition MarriageDeclaration Name Flags Card. Type Description & Constraints MarriageDeclaration 0..* Resource Marriage Declaration Resource Elements defined in Ancestors:id, meta, implicitRules, language #xD; identifier 0..* Identifier Business identifiers for the notification #xD; subject 0..1 Reference(Individual Person) Subject of the event (person the event happened to) #xD; eventDetail 0..1 string Free text note about the event #xD; placeOfRegistration 1..1 BackboneElement Place where this registration was officially created #xD; use 0..1 code home | work | temp | old | billing - purpose of this address #xD; type 0..1 code postal | physical | both - the type of address #xD; line 0..* string Street name, number, direction & P.O. Box etc. #xD; city 0..1 string Name of city, town etc. #xD; neighborhood 0..1 string Name of neighborhood, block #xD; postalCode 0..1 string Postal code for area #xD; parent C 0..1 BackboneElement Location hierarchy information #xD; code 0..1 code Simple code for the location type #xD; coding 0..1 Coding Coded representation of the location Binding: Birth Place Type Value Set (preferred) #xD; reference 0..1 Reference(Location) Reference to a Location resource #xD; name 0..1 string Text name of the location when structured data not available #xD; period 0..1 Period Time period when address was/is in use #xD; text 0..1 string Text representation of the address #xD; dateOfRegistration 1..1 date Date when this registration was officially created #xD; officer 1..1 Reference(Practitioner) Officer who registered the event #xD; spouse1 1..1 Reference(Individual Person) First spouse in the marriage #xD; spouse2 1..1 Reference(Individual Person) Second spouse in the marriage #xD; dateOfMarriage 1..1 date Date of marriage #xD; placeOfMarriage 0..1 BackboneElement Place where the marriage occurred #xD; use 0..1 code home | work | temp | old | billing - purpose of this address #xD; type 0..1 code postal | physical | both - the type of address #xD; line 0..* string Street name, number, direction & P.O. Box etc. #xD; city 0..1 string Name of city, town etc. #xD; neighborhood 0..1 string Name of neighborhood, block #xD; postalCode 0..1 string Postal code for area #xD; parent C 0..1 BackboneElement Location hierarchy information #xD; code 0..1 code Simple code for the location type #xD; coding 0..1 Coding Coded representation of the location Binding: Birth Place Type Value Set (preferred) #xD; reference 0..1 Reference(Location) Reference to a Location resource #xD; name 0..1 string Text name of the location when structured data not available #xD; period 0..1 Period Time period when address was/is in use #xD; text 0..1 string Text representation of the address #xD; typeOfMarriage 0..1 code Type of marriage Binding: Type of Marriage Value Set (extensible) #xD; marriageWitness 0..* Reference(Individual Person) Witnesses to the marriage #xD; marriageLicense 0..1 Identifier Marriage license identifier #xD; active 0..1 boolean is the resource active #xD; marriageNotification 0..1 Reference(Marriage Notification Resource) link toward the marriage notification #xD; Documentation for this format
A new base resource for capturing registered marriage data in the CRVS realm.
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
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())
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 its 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 its 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).
Business identifiers for the notification
Subject of the event (person the event happened to)
Place where this registration was officially created
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 managable, 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
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 managable, 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 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/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
home | work | temp | old | billing - purpose of this address
postal | physical | both - the type of address
Street name, number, direction & P.O. Box etc.
At least one of coding, code, reference, or name must be present
coding.exists() or reference.exists() or name.exists() or code.exists()
Text name of the location when structured data not available
Date when this registration was officially created