1 of 14

Document Ontology Committee

September 8, 2026

2 of 14

Welcome to the Document Ontology Committee Meeting

Please remain muted unless speaking.

Improve bandwidth

by closing excess windows & apps.

Agendas and other documentation can be found at loinc.org/committee/document-ontology/

For group discussions among the committee members, use the distribution email list-document-ontology@loinc.org

For issues or questions for the Regenstreif team, please contact documentontology@loinc.org

​

​

​

Submit questions

via the Q&A function

at any time.

3 of 14

Committee Meeting Agenda

Time

Topic

Action

Leads

2:00-2:05

Welcome

Informational

Rob McClure

Anil Patel

2:05-2:10

Discuss scheduling catch up out of cycle meeting in September

Informational

Rob McClure

Anil Patel

2:10-2:20

Standing Item: DO Analysis Subgroup updates

Informational

Rob McClure

Anil Patel

2.20-2:30

LOINC Document Ontology Title Case Fix

Informational

Rob McClure

Anil Patel

Steven Wagers

2:30-3:00

New code request

Discussion

Felicia Owens

​

​

​

​

4 of 14

Forum question

  • Display name for Document Ontology
    • Is there any plan in the near future for creating Document Ontology Display Names? Also, what is the rule used to build the Long Common Name and Short Name? We are seeing mixed of upper and lower case in both names in the LOINC db.
  • Document Name Changes- Latest ( Steven)

​

​

5 of 14

NEW CODE REQUEST

  • Submission 8477 (Canada Health Infoway )
  • Critical care Medicine Progress note {Setting}
    • Suggested using 64059-9 Critical care medicine Hospital Progress note
      • The 'Critical care progress note' code will be used on templates for Health Practitioners to use whilst they are following up on care in an ICU or NICU setting. There's a strong possibility that more than one template will exist with that code, depending on the role of the practitioner, the subspecialty (IM, surg, cardiology, neonatology). The Loinc code is not an ID for the templates, and is descriptive metadata, so this is not as issue.

​

6 of 14

NEW CODE REQUEST

  • Submission 8439 - Ian Bekker
  • New SMD to be added to the ontology
    • Forensic Pathology
    • Geriatric Psychiatry
    • Prehospital and Transport Medicine
    • Medical Biochemistry
    • Vitreoretinal
    • Adolescent and Young Adult Oncology
    • Neuromuscular Medicine

7 of 14

NEW CODE REQUEST

  • Submission 7747
  • Pregnancy Gestational Age Certificate
  • Submission note “Is a document issued by a medical professional that officially certifies the gestational age of pregnant woman. It's necessary for legal proof of gestation (e.g. for social benefits, time off work)
    • An official Social Security medical certificate form (Portugal) in which a licensed physician, based on ultrasound, certifies the gestational age (in weeks) and expected number of births for a specific pregnant woman, identified by name, DOB, social security number, and ID document; the supporting clinical information is documented in the medical record, and the signed certificate is used as legal proof of gestation for social benefits and employment protections. Validation of obstetric estimate of gestational age on US birth certificates - PMC

8 of 14

NEW CODE REQUEST

​

Submission 8601 & 8602-Lisa Nelson

Notification is being recognized as a Kind of Document (KOD), potentially as a Kind of Clinical Communication (KOCC).

Requested concept

Setting

Scale

Hospital Registration Notification

{Setting}

Doc

Matching Patient Notification

{Setting}

Doc

Submission 8626- Lisa Nelson

Guardianship Form - to support classification and exchange of guardianship-related information, but she believes the request also highlights broader questions about the LOINC Document Ontology axes. She suggests that “Information” may be a more flexible KOD than “Communication,” since the same content may be called Administrative Information when used as a structured document section but Administrative Communication when used to classify a FHIR Communication resource. She also emphasizes that labeling something a “Form” should not require it to be instantiated as a FHIR Questionnaire/QuestionnaireResponse, because many forms are represented as Compositions with structured sections and entries.

9 of 14

NEW CODE REQUEST

  • Submission 8071 (Lisa Nelson) SearchLOINC communication scale:doc (LOINC)
  • New codes for Communication
    • Communication Document
    • Communication
    • Social Care communication Document
    • Administrative communication Document
    • Financial communication Document
    • Legal communication Document

10 of 14

Doc Ontology - Clean up

  • How to define Doc ont Concepts?
  • How to use the rules / attributes in the DB and
  • How to follow as rules for modeling

​

  • Queries in tabs for each Doc Ont rule
  • Parts in wrong Doc Ont branch

11 of 14

Doc-Ontology Hierarchy

  • Doc.Ontology axis parts with no associated LOINC codes

​

  • Query results by HDS
  • Parts with no LOINC code

12 of 14

Document Ontology - Parts definitions

​

​

13 of 14

Next Steps

  • Next call: September 8th, 2026

​

14 of 14

Doc_Ont Analysis Sub committee