Canadian Ontology will change part display names, such as SMD values, to match Canadian medical vocabulary.
(Reference: 1)Use title case for display names of LOINC concepts. Example: Orthopaedic Surgery Diagnostic Study Note.
(Reference: 3)Unspecified part numbers will use the LOINC numeric code for unspecified part numbers.
(Reference: 4)Use "Unspecified" or "Blank" instead of { } for end/user systems showing an unspecified Part Display Name or Part Name.
(Reference: 5)The axis of our Ontology will be:
In addition to reference LOINC LCN, Short Name and Display Name, we'll have:
· Canadian English Display Name - we make Canadian from the LCN, algorithmically
· Canadian French Display Name. - we make Canadian from the LCN, algorithmically
· Canadian English Short Display Name - we make Canadian from the Short Name, algorithmically
· Canadian French Short Display Name - we make Canadian from the Short Name, algorithmically
· Canadian Provincial Display Name - based on French or English Display Name. This gives provincial flexibility, particularly if the law requires a certain display name, such as Power of Attorney or MAID. At this time, there is only room for one provincial alternative, but others can be made if there are multiple provinces.
· Canadian English Long Common Name - to use as our LCN but it has Canadian terms.
(Reference: 7)Preferred Discharge Summary type is:
Type: Discharge Summary
Other axis: Suppressed
(Reference: 8)The action of admitting someone to the hospital is captured in the ToS = Admission Evaluation.
SMD can be used.
Role is only used for non-physicians
Setting is suppressed or can be "LTC"
(Reference: 9)SMD is primary way to classify a document and Admission notes are for hospitals, not wards. E.g. An "ICU Admission" is a "Critical Care Transfer Note". i.e ToK = 'Transfer Summary' with SMD = the receiving discipline
(Reference: 10)Ontology will be in four files:
(1) Human Readable (XLSX, each are a worksheet)
o Combined Descriptors and Parts (similar to ON)
o pCLOCD format (additional columns to match, the ‘nomenclature’ sheet)
Machine Processable (each are tab delimited files)
(2) LOINC Descriptors. (Not the parts)
(3) LOINC Parts (LNC_PartLinkPrimary) (Parts and Identifier, not the display name)
(4) The provincial descriptors file
Also add the history information to the file.
(Reference: 11)The metadata of documents being distributed MUST include an appropriate numeric identifier from the Canadian Document Ontology.
· “Appropriate”: the content of the document matches the common interpretation of the Long Common Name or the definition defined by Canadian Document Ontology.
· Must contain: A Canadian Display Name
· MAY contain: Part axis values and identifier, Local Name, Other display names
(Reference: 12)The expectations of health system who are receiving a document expediently (without time for a normal information exchange agreement to be set up, exchange of document code mapping and testing to be done)
SENT DOCUMENT | EHR | Repository | EMR |
Has Canadian LOINC that is used in receiving system | Accept in normal patient chart structure | Accept in EHR - Certain document types can be excluded from viewing on a policy basis | Accept in EMR |
Has Canadian LOINC that is NOT used in receiving system | Accept in Miscellaneous document structure (visible, trackable) Or Matched to more generalized LOINC code | All Canadian LOINC codes are accepted in Repositories. Certain document types can be excluded from viewing on a policy basis | Accept in Miscellaneous document structure (visible, trackable) User is warned |
Does NOT have Canadian LOINC code or is missing a code | Accept in Miscellaneous document structure (visible, trackable) Inform Sender | Accept in Miscellaneous document structure (visible, trackable) Inform sender | Accept in Miscellaneous document structure (visible, trackable). The user is warned EMR vendor is notified |
Type of Service = Consultation
SMD: Most of those available
Role: Suppressed
Setting: Suppressed
(Reference: 14)