| TEMPLATE ID | Case demographic information - JM |
|---|---|
| Concept | Case demographic information - JM |
| Description | Not Specified |
| Purpose | Not Specified |
| References | |
| Authors | date: 2022-08-03 |
| Other Details Language | date: 2022-08-03 |
| Other Details (Language Independent) |
|
| Language used | en |
| Citeable Identifier | 1013.26.916 |
| Root archetype id | openEHR-EHR-SECTION.adhoc.v1 |
| Case demographic information | Case demographic information: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Adult demographics | Adult demographics: A container archetype used to hold demographic-related EHR CLUSTER archetypes. |
| Data | |
| Person - adult patient | Person - adult patient: An individual human being. |
| Structured name of a person - full | Structured name of a person - full: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Middle name | Middle name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Nickname | Nickname: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'.
|
| National Insurance Scheme Number | National Insurance Scheme Number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Address - Local + GIS | Address - Local + GIS: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Geolocation code | Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash. |
| Latitude | Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° |
| Longitude | Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° |
| Map URL | Map URL: Link to a location on an online map. For example: a location on a Google or iOS map. |
| Phone - personal mobile | Phone - personal mobile: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication. |
| Phone - home landline | Phone - home landline: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication. |
| Phone - work number | Phone - work number: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication. |
| Email: Details about a specified type of electronic communication. | |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Comment | Comment: Additional narrative about the electronic communication not captured in other fields. |
| Child demographics | Child demographics: A container archetype used to hold demographic-related EHR CLUSTER archetypes. |
| Data | |
| Person - child patient | Person - child patient: An individual human being. |
| Structured name of a person - full | Structured name of a person - full: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Middle name | Middle name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Nickname | Nickname: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Suffix | Suffix: One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components. Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'.
|
| National Insurance Scheme Number | National Insurance Scheme Number: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Address - Local + GIS | Address - Local + GIS: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Geolocation code | Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash. |
| Latitude | Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° |
| Longitude | Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° |
| Map URL | Map URL: Link to a location on an online map. For example: a location on a Google or iOS map. |
| Phone - home landline | Phone - home landline: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication. |
| Phone - personal mobile | Phone - personal mobile: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication. |
| Email: Details about a specified type of electronic communication. | |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Comment | Comment: Additional narrative about the electronic communication not captured in other fields. |
| Person - nameless infant patient | Person - nameless infant patient: An individual human being. |
| Label | Label: A label for the individual. For example: 'Neighbour in the house with the red door'.
|
| Structured name of woman - full + maiden | Structured name of woman - full + maiden: Discrete components of an individual's name. |
| Title | Title: One or more honorific form(s) of address commencing a name. Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'.
|
| First name | First name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Middle name | Middle name: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Nickname | Nickname: One or more unique name(s) used to identify an individual within a family group. Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case. |
| Last name | Last name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Maiden name | Maiden name: One or more name(s) that an individual has in common with a family group. Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string. |
| Jamaica Digital Health ID | Jamaica Digital Health ID: Identifier associated with the individual. Occurrences for this data element is set to 0..* to allow for more than one Identifier to be recorded. Note that the DV_IDENTIFIER data type contains multiple subcomponents for recording the ID value, type, issuer and assigned. For example - social security number; driver's license; or passport number. |
| Address - Local + GIS | Address - Local + GIS: Details about the location of a person, physical building or landmark. |
| Street address | Street address: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Landmark | Landmark: An unstructured address line representing all relevant street-level or post-box details that would support the identification of a location. Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'. |
| Community | Community: The name of the lowest level locality that contains the address. For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
|
| Parish | Parish: The name of a local government district or geographical area that contains the address. Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
|
| Country | Country: The name of the country containing the address. For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
|
| Geolocation code | Geolocation code: Unique identifier that represents a precise geographical location. Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash. |
| Latitude | Latitude: Horizontal (y) coordinate of a geolocation for the address. Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093. -90..90 ° |
| Longitude | Longitude: Horizontal (x) coordinate of a geolocation for the address. Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694. -180..180 ° |
| Map URL | Map URL: Link to a location on an online map. For example: a location on a Google or iOS map. |
| Phone - home landline | Phone - home landline: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication. |
| Phone - personal mobile | Phone - personal mobile: Details about a specified type of electronic communication. |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Purpose | Purpose: The purpose or use for the identified type of electronic communication. |
| Email: Details about a specified type of electronic communication. | |
| Type | Type: The type or form of electronic communication. The DV_CODED_TEXT value set supports recording of the most common electronic communications used in health. If other alternatives are required the DV_TEXT data type can be used to record other types of electronic communication such as social media or video conferencing URLs within a template. |
| Value | Value: The unique combination of alphanumeric characters, relevant for representation of 'Type'. For example: area code + landline phone/pager number; country code + mobile phone number; or email address. |
| Comment | Comment: Additional narrative about the electronic communication not captured in other fields. |
| Date of birth | Date of birth: Overview or summary record of the pregnancy and birth of an individual. |
| Data | |
| Date of birth | Date of birth: The date/time of birth of the individual. May also be used to record the assumed or agreed date/time of birth for operational purposes, if the actual date/time is not formally recorded. Possible alternatives for the date/time of birth of the individual can be recorded using the CLUSTER.DOB_alternative archetype 'Date of birth details' SLOT. Partial dates are allowed. |
| Age assertion | Age assertion: A statement about the age of an individual at a point in time. |
| Data | |
| Point in time event | Point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time. |
| Data | |
| Chronological age | Chronological age: The age of an individual at the event time, calculated from date of birth. In most use cases the DV_DURATION data type is used to record the Chronological age. The DV_INTERVAL_DURATION is used for recording a structured age interval in cases where there's uncertainty about the individual's exact age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days). The DV_TEXT data type is used for recording a textual representation of the individual's age, or age category often found in questionnaires. For example: 'P3M2W', '0,2884615384615385 a_j', '3 months 2 weeks' or '31-40 years' or 'Teenager'. P1M..P200Y Units:
|
| Age assertion - infant | Age assertion - infant: A statement about the age of an individual at a point in time. |
| Data | |
| Point in time event | Point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time. |
| Data | |
| Chronological age | Chronological age: The age of an individual at the event time, calculated from date of birth. In most use cases the DV_DURATION data type is used to record the Chronological age. The DV_INTERVAL_DURATION is used for recording a structured age interval in cases where there's uncertainty about the individual's exact age. The DV_QUANTITY data type is used for recording a decimal age in years or mean Julian years (365.25 days). The DV_TEXT data type is used for recording a textual representation of the individual's age, or age category often found in questionnaires. For example: 'P3M2W', '0,2884615384615385 a_j', '3 months 2 weeks' or '31-40 years' or 'Teenager'. PT1H..P51W |
| Sex & gender | Sex & gender: Details about the gender of an individual. |
| Data | |
| Sex assigned at birth | Sex assigned at birth: The sex of an individual determined by anatomical characteristics observed and registered at birth. For example: 'Male', 'Female', 'Intersex'. Coding with a terminology is recommended, where possible. Use the element 'Comment' or the SLOT 'Details' if needed to register more specific details of the individuals gender.
|
| Sex & gender - newborn | Sex & gender - newborn: Details about the gender of an individual. |
| Data | |
| Sex assigned at birth | Sex assigned at birth: The sex of an individual determined by anatomical characteristics observed and registered at birth. For example: 'Male', 'Female', 'Intersex'. Coding with a terminology is recommended, where possible. Use the element 'Comment' or the SLOT 'Details' if needed to register more specific details of the individuals gender.
|