| ARCHETYPE ID | openEHR-EHR-EVALUATION.developmental_milestones.v0 |
|---|---|
| Concept | Developmental milestone summary |
| Description | Summary information about the achievement of developmental milestones for an individual, usually a child, to monitor progress over time. |
| Use | Use to record an overview of developmental progress across all age-appropriate milestones and details about each specific milestone. Parents or caregivers may report the achievement and associated date for each milestone, for example in the context of a personal health record; however, assessments of age-appropriate progress or variations from typical development should be recorded only by a healthcare professional. |
| Purpose | To record an overview of developmental progress across all age-appropriate milestones and details about each specific milestone. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2021-03-01 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2021-03-01 |
| Other Details (Language Independent) |
|
| Keywords | childhood, infant, baby, achievement, toddler, child |
| Lifecycle | in_development |
| UID | f336cdef-3359-4135-9ad2-b226c9c78062 |
| Language used | en |
| Citeable Identifier | 1013.1.5244 |
| Revision Number | 0.0.1-alpha |
| data | |
| Overall status | Overall status: Statement describing the current level of achievement across all age-appropriate milestones. Choice of:
|
| Overall description | Overall description: Narrative summary about the individual’s overall progress in achieving developmental milestones. |
| Overall trajectory | Overall trajectory: The observed pattern or direction of an individual's developmental progress over time, relative to age-based expectations. Coding with an external terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available.
|
| Per milestone | Per milestone: Details about each individual milestone. Record one instance of this cluster per milestone. |
| Milestone name | Milestone name: Name of the developmental milestone. For example: walking independently, speaking first words, and using a pincer grasp to pick up small objects. Coding with an external terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available. |
| Category | Category: Name of the developmental domain associated with the identified milestone. Each category is used to classify milestones into commonly recognised areas of child development and to support monitoring of progress at the domain level. Coding with an external terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available. Choice of:
|
| Trajectory | Trajectory: The observed pattern or direction of an individual's developmental progress over time, related to an identified milestone and relative to age-based expectations. Coding with an external terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available.
|
| Status | Status: Statement describing the current level of achievement for the identified milestone. "Reported as achieved" may be used to support documentation by carers or others when the milestone achievement is entered into a citizen's health record but cannot be directly witnessed or verified by a clinician. Coding with an external terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available.
|
| Date achieved | Date achieved: The date when the milestone was reached. The younger the child, especially under 1 year, the greater the precision expected, but approximations are acceptable when this is the only information available and clearly identified as such in the health record, for example '~August 1, 2025'. For older children, or when information is recorded long after the event, partial dates such as month and year may be recorded. Where only an age is known, it should be converted to an approximate date and recorded using this data element. |
| Date of assertion | Date of assertion: The date when the milestone was assessed. The date on which the 'Status' for the identified 'Milestone name' is documented. |
| Variation | Variation: Narrative description about the deviation from normal development. For example, include commentary about the child belly crawling instead of typical hands-and-knees crawling. |
| Reason for delay | Reason for delay: Identification of the reason for delay in achievement of milestones. For example: prematurity, Down syndrome, recurrent ear infections, Autism Spectrum Disorder (ASD). Coding with an external terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available. Choice of:
|
| Reason for regression | Reason for regression: Identification of the reason for regression in achievement of milestones. For example: emotional neglect; neurodegenerative disease, hearing loss, or Autism Spectrum Disorder (ASD). Coding with an external terminology is recommended. Free text entry should only be permitted if no appropriate coded value is available. Choice of:
|
| Additional details | Additional details: Additional structured details about the identified milestone. Include: All not explicitly excluded archetypes |
| Comment | Comment: Additional narrative about the individual's developmental progress related to the identified milestone not captured in other fields. |
| Additional details | Additional details: Additional structured details about all milestone summary. Include: All not explicitly excluded archetypes |
| Overall comment | Overall comment: Additional narrative about the individual's overall developmental progress not captured in other fields. |
| protocol | |
| Last updated | Last updated: The date when the developmental milestones record was last updated. |
| Extension | Extension: Additional information required to extend the model with local content or to align with other reference models or formalisms. For example: local information requirements; or additional metadata to align with FHIR. Include: All not explicitly excluded archetypes |
| Other contributors | Hildegard Franke, freshEHR Clinical Informatics Ltd., United Kingdom Kim Drever, Kudos Paediatrics, Australia Nyree Taylor, CSIRO, Australia |
| Translators |