Generated Narrative: StructureDefinition register-client-model Name Flags Card. Type Description & Constraints register-client-model 0..* Base NG-Imm-C5 RegisterClient #xD; identifier 1..1 string Unique identifier for clients including the national identification number, medical records number, immunization information system ID, and others. #xD; name 1..1 BackboneElement The full name of the client. #xD; family 1..1 string Client's family name or last name. #xD; given 1..1 string Client's first name or given name. #xD; sex 1..1 CodeableConcept Sex Binding: NG Gender or Sex VS (preferred) #xD; dateOfBirth 1..1 date Client's date of birth (DOB) if known. If unknown, use assigned DOB for administrative purposes. #xD; ageInWeeks 0..1 integer The client's calculated age (number of weeks) based on the date of birth and the visit date. #xD; ageInMonths 0..1 integer The client's calculated age (number of months) based on the date of birth and the visit date. #xD; ageInYears 0..1 integer The client's calculated age (number of years) based on the date of birth and the visit date. #xD; weightAtBirth 0..1 Quantity Client's weight at birth in kg. #xD; address 0..1 BackboneElement Client's residential address. #xD; residentialAddress 0..1 string Child's residential address. #xD; houseNumber 0..1 string The number of the house where the client lives. #xD; village 0..1 string The village where the client lives. #xD; town 0..1 string The town or city where the client resides. #xD; ward 0..1 CodeableConcept The ward where the client lives. Binding: NG-Imm Wards VS (preferred) #xD; lga 0..1 CodeableConcept Local Government Authority where the client lives. Binding: NG-Imm LGAs VS (preferred) #xD; state 0..1 CodeableConcept The state where the client lives. Binding: NG-Imm States VS (preferred) #xD; contact 0..* BackboneElement The client's caregiver (person) which could be next of kin (e.g., partner, husband, mother, sibling, etc.). #xD; name 1..1 BackboneElement The full name of the caregiver. #xD; family 1..1 string Family name of the caregiver. #xD; given 1..1 string Given name of the caregiver. #xD; telecom 0..* ContactPoint Phone number of the caregiver. #xD; system 1..1 code Type of communication (e.g., phone, email). #xD; value 1..1 string Caregiver's contact number or address. #xD; relationship 0..1 CodeableConcept The relationship of the caregiver to the client. #xD; text 0..1 string Caregiver relationship display text. #xD; otherChildren 0..* BackboneElement Any other children the mother has. #xD; name 1..1 string The full name of the mother's other children. #xD; birthYear 1..1 integer The year the mother's children were born. #xD; sex 1..1 CodeableConcept Biological characteristics that define humans as female or male. Binding: NG Gender or Sex VS (preferred) #xD; healthStatus 0..1 CodeableConcept Overall physical, mental, and emotional well-being of the sibling. Binding: NG-Imm Sibling Health Status VS (preferred) #xD; hivStatus 0..1 CodeableConcept HIV status of the client. Binding: NG-Imm Client HIV Status VS (preferred) #xD; pregnancyStatus 0..1 CodeableConcept Confirms whether the client is pregnant or not. Binding: NG-Imm Clinical Status VS (preferred) #xD; Documentation for this format
Nigeria Primary Healthcare Development Agency.
IMMZ.C5 - A logical model representing a client being registered in the immunization system.
Unique identifier for clients including the national identification number, medical records number, immunization information system ID, and others.
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")])
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 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 element that contains them
Documentation of a specific instance of sex information for the client.
Client's date of birth (DOB) if known. If unknown, use assigned DOB for administrative purposes.
The client's calculated age (number of weeks) based on the date of birth and the visit date.
The client's calculated age (number of months) based on the date of birth and the visit date.
The client's calculated age (number of years) based on the date of birth and the visit date.
The number of the house where the client lives.
The town or city where the client resides.
Local Government Authority where the client lives.
The client's caregiver (person) which could be next of kin (e.g., partner, husband, mother, sibling, etc.).
A system is required if a value is provided.
not(exists(f:value)) or exists(f:system)
Type of communication (e.g., phone, email).
Telecommunications form for contact point.
Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
Need to support legacy numbers that are not in a tightly controlled format.
home | work | temp | old | mobile - purpose of this contact point
Identifies the purpose for the contact point.
Applications can assume that a contact is current unless it explicitly says that it is temporary or old.
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one
Specify preferred order of use (1 = highest)
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
Note that rank does not necessarily follow the order in which the contacts are represented in the instance.
Time period when the contact point was/is in use
Time period when the contact point was/is in use.
The relationship of the caregiver to the client.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
The full name of the mother's other children.
The year the mother's children were born.
Biological characteristics that define humans as female or male.
Overall physical, mental, and emotional well-being of the sibling.
Confirms whether the client is pregnant or not.