Operative note findings

General Details:

Name:
Operative note findings
Steward:
LOINC
Registration Status:
Qualified

Permissible Values:

Data Type:
Text
Unit of Measure:
Ids:
Value Code Name Code Code System Code Description

Designations:

Designation:
Operative note findings
Tags:
Short Name
Designation:
Surgical operation note findings Narrative
Tags:
Long Common Name

Properties:

Key:
Related Names
Value:
EncounterEvaluation and managementEvaluation and management note
FindingFindingsH+P
H+P.SURGICAL PROCEDURESNarrativenotes
Operative noteOperative note findingsP prime
Point in timeRandomReport
SurgVisit note
Key:
Related Codes
Value:
Code SystemCodeCode TextCode Version
https://www.phenxtoolkit.orgPX161602450600PX161602_Surgery_1_Results
Key:
Fully-Specified Name
Value:
ComponentPropertyTimeSystemScaleMethod
Surgical operation note findingsFindPt^PatientNar
Key:
Basic Attributes
Value:
ClassTypeFirst ReleasedLast UpdatedChange Reason
H&P.SURG PROCClinicalVersion 1.0iVersion 2.63Because it is too difficult to maintain and because the distinction between documents and sections is not clear-cut nor necessary in most cases, the DOCUMENT_SECTION field has been deemed to have little value. The field has been set to null in the December 2017 release in preparation for removal in the December 2018 release. These changes were approved by the Clinical LOINC Committee.

Identifiers:

Source:
NLM
Id:
7krxqP5o2og
Version:
1.1
Source:
LOINC
Id:
10215-2
Version:
2.69