This proposal is on hold for potential future use.
Project 1128 
Clinical Notes allow EHR users to view and enter textual information that is stored in the patient's chart.
Notes can be developed in many different ways:
Clinical Notes could be as simple as a single sentence or as comprehensive as a History & Physical (H&P). ClinicalNotes can range from pure narrative to partial narrative to fully encoded, but it is more commonly narrative and less commonly fully encoded (since it may not be efficient to do so). Often the structure of the narrative is just a bold piece of text signifying a section heading within the note. Clinical Notes can be authored by a physician, nurse, pharmacist, or any other practitioner. Note types, such as H&P, Consult Note, Progress Note, Operative Note, Nursing Note, Physician Communication, Pharmacy Intervention Note, Rehab Note, and Nutrition Therapy Note as well as date, author, status, and encounter help organize notes.
|Type||Contents||Author||Context||Point in Time|
|Physician Inpatient Expectation||CMS 2 midnight rule; physician attesting to why the patient needs to remain in the hospital (if no admitting order within 24 hours)||Physician||Encounter||Yes|
|Office Note or ED Note||Chief Complaint, HPI, Review of Systems, Physical Exam, Subjective/Constitutional, Assessment/Impression and Plan (orders), Follow-Up, Billing Notes, Chart data||Physician||Encounter||Yes|
|H&P||Diagnosis/Chief Complaint, Advance Directive, HPI, Past Medical History, Family/Social History, Chart Data (allergies, meds), Review of System, Physical Exam, Assessment and Plan (more comprehensive than the Office Note)||Physician||Encounter||Yes|
|Consult Note||similar to H&P, except only comprehensive within a given specialty||Physician||Encounter||Yes|
|Inpatient Progress Note||SOAP format or freetext format (used when something significant happens after the day's progress note was already written)||Physician||Encounter||Yes|
|Operative Note||Date of Surgery, Surgeon, Assistant, Pre-Op Dx, Post-Op Dx, Operation/procedure codes, Anesthesiologist, Anesthesia used, complications, estimated blood loss, specimens removed, description of surgery/findings (instruments used, etc.)||Physician||Procedure||Yes|
|Shift (Nursing Progress) Note||Major events of the shift, such as:||Nurse||Encounter||Yes|
|Physician Communication||Communication for various reasons, such as:||Anyone||Encounter||Yes|
|Pharmacy Intervention Note||Pharmacist reviews medications; found patient was on duplicate therapy or found cheaper therapy; actions the pharmacist took or is recommending; billing note about pharmacist time spent;||Pharmacist||Encounter||Yes|
|Pharmacy Monitoring Note||Anticoagulation (monitor labs, intervene if unsafe); Antibiotics||Pharmacist||Encounter||Yes|
|Rehab Notes (OT, Speech, PT)||Chief Complaint, HPI, Physical Therapy Assessment, Treatment, Plan, Goals, Billing||Rehab Services||Encounter||Yes|
|Nutrition Therapy Note||general note, overall dietary note with tube feeding, amount taken orally, how doing with meals, estimated % of caloric intake or protein intake, admit weight to current weight comparison, labs, medications, nutrition diagnosis, RD recommendations, measurable goals||RD||Encounter||Yes|
|Physician Clarification Request from Medical Records (HIM query)||example: Anemia Specificity; Coder will pull things out of chart and say I was confused by these facts....physician(s) reply by comments on the note or addendums on the note||Medical Records||Encounter||Yes|
The following describes limitations with using existing resources to convey Clinical Notes.
For a subset of use cases, only when the clinical note type conveys that the contents are specific to a single resource, the resource-specific Narrative (DomainResource.text.div) was considered because the DomainResource.text Narrative  is a "human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative."
The primary drawback to using resource-specific narrative is that it doesn't cover all use cases (when the content of the note spans multiple resources). Secondarily, it could prevent us from identifying the actual note body if the narrative also includes other attributes, such as author, date/time, etc. For example, the section ‘HPI’ as a pure narrative, included in a composition ‘Admission H&P’ where:
The ClinicalImpression  is a "record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition." However, a Clinical Note could have one or more Clinical Impressions, which are typically part of a section named "Assessment/Plan", but not all Clinical Notes contain Clinical Impressions. Because notes are a form of human communication, nearly anything can be described in the narrative of a clinical note. Regardless of this breadth, most EHR systems use the same workflow and user interface to capture the narrative. The clinical note narrative can be condition-oriented (e.g. SOAP) or more administrative in nature, such as communicating patient transportation arrangements, phone calls, or when the family members will be available to talk to physician, etc.
Because "a Composition  defines the structure, it does not actually contain the content" there is a need for a resource that defines the narrative content within a clinical note.
Although Observation could work, the distinction is more that Observation is not intuitive since these concepts are often treated separately in EHR workflows. Specifically, it is not intuitive that the note's title is representation as an Observation.code.text. Furthermore, a note could have other involved parties or actors, such as when the note is scribed or dictated whereas most Observations typically focus on a performer.
Because Annotation is a data type, Annotations are not discoverable on their own. Workflow capabilities (e.g. read/unread, review/cosignature) are not features of an annotations. Furthermore, additional codified attributes, such as note type, are not available via Annotations. The FHIR Annotation  data type is meant to be a collection of "text note which also contains information about who made the statement and when" in context of another resource (e.g. AllergyIntolerance, Procedure, MedicationOrder, Encounter). As such, a benefit of using a separate resource for Clinical Note is that there could be users who have privileges to create a Clinical Note, but might not have privileges to modify the resource-specific annotation.
Lloyd McKenzie and/or Michelle M Miller
When you have completed your proposal, please send an email to FMGcontact@HL7.org