-
Notifications
You must be signed in to change notification settings - Fork 4
Home
For a general explanation of what Medical Markdown actually is and its main concepts, see the README.md at the top level of the Medical Markdown repository.
- Headings and Subheadings are delineated by a small number of characters, followed by a forward-slash character. eg
DH/
- They must be at the beginning of a line to count as a heading. This avoids inappropriate parsing of text in sentences into structured data.
- Subsequent lines are then regarded as structured under that heading. Depending on the heading type, the content may either be paragraph text, a bulleted list, ordered list, or other form of data. See the individual data items for specifics.
- A blank newline marks the end of the section. Ignore non-printing characters such as spaces or tabs.
- Tags are not case sensitive.
DH/
===dh/
===dH/
===Dh/
(but: are there any situations where it would help for them to be case sensitive? I'm open to viewpoints here)
- anything in backticks '`'' is something the user types in
- the rocket '=>'' indicates the resultant output from the parser
Over time I will work to make the recommended outputs compliant with FHIR messaging and/or openEHR archetypes that are available, so please for now consider the structured data expansion examples to be 'indicative of the concept', and not a precise mandated output or defined standard. Yet.
- Heading: "Presenting complaints or issues"
- Clinical description: The list and description of the health problems and issues experienced by the patient resulting in their attendance. These may include disease state, medical condition, response and reactions to therapies. Eg blackout, dizziness, chest pain,follow up from admission, falls, a specific procedure, investigation or treatment.
History of the Presenting Complaint(s)
- Heading: "Family history"
- Clinical description: The record of relevant illness in family relations deemed to be significant to the care or health of the patient, including mental illness and suicide, genetic information etc.
The section tag OE/
demarcates an 'On Examination' section. Within an on examination section, you can use the following tags to create structured data:
example: PR/ 87 reg
=> { "pulse": {
"rate":"87",
"units": "min-1",
"regularity": "regular"
}
BP/
blood pressure
GCS/
Glasgow Coma Scale (Assessment Scale)
this score can be further broken down into its consituent parts for Best Eye, Verbal, and Motor responses:
example: GCS/ 15
=> {"glasgow-coma-scale": "15"}
AVPU/
Alert - Voice - Pain - Unresponsive
example AVPU/ A
=> {"avpu":"alert"}
RS/
Respiratory System
- free text or coded data SNOMED (finding)
CVS/
Cardiovascular System
HS/
heart sounds
- free text or coded data SNOMED (finding)
-
1+2+0
signifies1st and 2nd heart sound heard, no additional sounds
and could be represented in appropriate SNOMED (finding) codes
PNS/ Peripheral Nervous System
CNS/ Central Nervous System
IMP/ Impression (this is used often in place of Diagnosis as it is less categorical)
PLAN/ Plan
TODO/ A todo or jobs list
- bulleted list
- assign via @
- context via #
- (use todo.txt spec)