|
About the loinc-implementation category
|
|
0
|
75
|
June 23, 2023
|
|
COVID and Prerelease pages inconsistent
|
|
4
|
57
|
June 23, 2023
|
|
LOINC Maintenance in Cerner
|
|
4
|
77
|
June 23, 2023
|
|
LOINC Implementation Helpful Suggestions
|
|
6
|
104
|
June 23, 2023
|
|
LOINC Answer Lists independent use
|
|
1
|
96
|
June 23, 2023
|
|
Data missing between versions.
|
|
3
|
121
|
June 23, 2023
|
|
LOINC table file database engine
|
|
1
|
87
|
June 23, 2023
|
|
Choosing between using on outside vendor to do mapping versus doing it yourself
|
|
2
|
71
|
June 23, 2023
|
|
Answer Lists
|
|
2
|
88
|
June 23, 2023
|
|
What to do with map to file
|
|
3
|
84
|
June 23, 2023
|
|
Sending textual comments
|
|
2
|
109
|
June 23, 2023
|
|
Inconsistencies in LinguisticVariants format
|
|
5
|
91
|
June 23, 2023
|
|
UCUM composition
|
|
1
|
73
|
June 23, 2023
|
|
Using LOINC to link results from labs
|
|
3
|
74
|
June 23, 2023
|
|
CSV structure for copyrights
|
|
1
|
77
|
June 23, 2023
|
|
LOINC implementation for Genetic Cancer Labs
|
|
2
|
82
|
June 23, 2023
|
|
LOINC database and multi-axial hierarchy out of sync?
|
|
3
|
103
|
June 23, 2023
|
|
Jumping Off
|
|
2
|
71
|
June 23, 2023
|
|
LOINC database and multi-axial hierarchy out of sync?
|
|
1
|
90
|
June 23, 2023
|
|
Short Name vs. all components in HL7
|
|
2
|
103
|
June 23, 2023
|
|
Best practice for maintaining multiple versions?
|
|
3
|
72
|
June 23, 2023
|
|
LOINC Adopters Directory on loinc.org
|
|
1
|
72
|
June 23, 2023
|
