ARCHETYPE Menstrual diary (openEHR-EHR-OBSERVATION.menstrual_diary.v1)

ARCHETYPE IDopenEHR-EHR-OBSERVATION.menstrual_diary.v1
ConceptMenstrual diary
DescriptionDetails about menstrual bleeding and associated symptoms within a specified day.
UseUse to record details about menstrual bleeding and associated symptoms within a specified day. For example in a period tracker or diary.
MisuseNot to be used to record the Last menstrual period (LNMP) use the EVALUATION.last_menstrual_period archetype for this purpose. Not to be used to record overall information about menses or related symptoms in a cycle, use the OBSERVATION.menstruation archetype for this purpose. Not to be used to record details about menarche or menopause, use the EVALUATION.menstruation_summary archetype for this purpose. Not to be used to record information about an individual's menstruation history events or patterns of menstruation over time, use the EVALUATION.menstruation_summary archetype for this purpose.
PurposeTo record details about menstrual bleeding and associated symptoms within a specified day.
References
Copyright© openEHR Foundation
AuthorsAuthor name: Marit Alice Venheim
Organisation: Helse Vest IKT AS
Email: marit.alice.venheim@helse-vest-ikt-no
Date originally authored: 2021-08-03
Other Details LanguageAuthor name: Marit Alice Venheim
Organisation: Helse Vest IKT AS
Email: marit.alice.venheim@helse-vest-ikt-no
Date originally authored: 2021-08-03
Other Details (Language Independent)
  • Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
  • Custodian Organisation: openEHR Foundation
  • Original Namespace: org.openehr
  • Original Publisher: openEHR Foundation
  • Custodian Namespace: org.openehr
  • MD5-CAM-1.0.1: 4C6F48B1E36EF19CB4B0045F77AF59C1
  • Build Uid: 6b994416-c181-44ee-850c-0e505099c99c
  • Revision: 1.0.1
Keywordsmenstruation, menses, cycle, menstrual, dysmenorrhoea, pain, bloating
Lifecyclepublished
UID53547e9c-0458-4436-936e-5969248c5300
Language useden
Citeable Identifier1246.145.2793
Revision Number1.0.1
protocol
ExtensionExtension: Additional information required to capture local content or to align with other reference models/formalisms.
For example: local information requirements or additional metadata to align with FHIR.
Include:
All not explicitly excluded archetypes
data
FlowFlow: Semi-quantitative estimation of menstrual flow per day.
Choice of:
  •  Coded Text
    • Flooding [For example a presence of heavy menstrual flow that exceeded capacity of menstrual products to absorb the flow.]
    • Heavy flow [For example needing to change a high-absorbency tampon or pad every one to four hours.]
    • Medium flow [For example needing to change a regular-absorbency tampon or pad every three to four hours.]
    • Light flow [For example needing to change a low- or regular-absorbency tampon or pad one to three times per day.]
    • Spotting [For example a drop or two of blood, not even requiring menstrual products.]
    • No bleeding [No menstrual bleeding.]
  •  Text
VolumeVolume: Estimated volume of menstrual blood loss in any 24hr time period.
For example estimating the volume based on a pictorial blood loss assessment chart.
Property: Volume
Units: ml
Blood clotsBlood clots: Presence of blood clots.
  • Present [Blood clots occurred during the menstrual flow.]
  • Absent [Blood clots did not occur during the menstrual flow.]
ColorColor: Color of blood.
DescriptionDescription: Narrative description of the menstrual cycle on the day in question. For example day 2.
Additional detailsAdditional details: Additional details about the specific day of the menstrual cycle.
For example menstrual symptoms or pictorial blood loss assessment charts.
Include:
openEHR-EHR-CLUSTER.symptom_sign.v1 and specialisations
CommentComment: Additional narrative about the specific day of the menstrual cycle, not captured in other fields.
events
Any eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Per dayPer day: To record a spesific single day in a cycle.
Interval width: 24 hours
Other contributorsVebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)
Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)
SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India
Sigrid Daae Mæland, Helse Vest IKT, Norway
Peter Fedorcsak, Oslo universitetssykehus, Norway
Heather Grain, Llewelyn Grain Informatics, Australia
Mikkel Johan Gaup Grønmo, Forvaltningssenter EPJ, Helse-Nord, Norway (openEHR Editor)
Evelyn Hovenga, EJSH Consulting, Australia
Jörgen Kuylenstierna, eWeave AB, Sweden
Liv Laugen, ​Oslo University Hospital, Norway, Norway (openEHR Editor)
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
Anna Moore, University of Cambridge, United Kingdom
Lars Morgan Karlsen, Nordlandssykehuset Bodø, Norway
John Tore Valand, Helse Bergen, Norway (openEHR Editor)
Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor)
Translators
  • Norwegian Bokmål: Marit Alice Venheim, John Tore Valand, Helse Vest IKT, Helse Bergen, marit.alice.venheim@helse-vest-ikt.no, john.tore.valand@helse-vest-ikt.no
  • Dutch: Jan Henk Heilersig, Nedap Healthcare, janhenk.heilersig@nedap.com