About the loinc-implementation category
|
|
0
|
89
|
June 23, 2023
|
COVID and Prerelease pages inconsistent
|
|
4
|
77
|
June 23, 2023
|
LOINC Maintenance in Cerner
|
|
4
|
95
|
June 23, 2023
|
LOINC Implementation Helpful Suggestions
|
|
6
|
123
|
June 23, 2023
|
LOINC Answer Lists independent use
|
|
1
|
129
|
June 23, 2023
|
Data missing between versions.
|
|
3
|
139
|
June 23, 2023
|
LOINC table file database engine
|
|
1
|
107
|
June 23, 2023
|
Choosing between using on outside vendor to do mapping versus doing it yourself
|
|
2
|
116
|
June 23, 2023
|
Answer Lists
|
|
2
|
101
|
June 23, 2023
|
What to do with map to file
|
|
3
|
121
|
June 23, 2023
|
Sending textual comments
|
|
2
|
129
|
June 23, 2023
|
Inconsistencies in LinguisticVariants format
|
|
5
|
112
|
June 23, 2023
|
UCUM composition
|
|
1
|
98
|
June 23, 2023
|
Using LOINC to link results from labs
|
|
3
|
93
|
June 23, 2023
|
CSV structure for copyrights
|
|
1
|
94
|
June 23, 2023
|
LOINC implementation for Genetic Cancer Labs
|
|
2
|
95
|
June 23, 2023
|
LOINC database and multi-axial hierarchy out of sync?
|
|
3
|
145
|
June 23, 2023
|
Jumping Off
|
|
2
|
108
|
June 23, 2023
|
LOINC database and multi-axial hierarchy out of sync?
|
|
1
|
121
|
June 23, 2023
|
Short Name vs. all components in HL7
|
|
2
|
125
|
June 23, 2023
|
Best practice for maintaining multiple versions?
|
|
3
|
89
|
June 23, 2023
|
LOINC Adopters Directory on loinc.org
|
|
1
|
93
|
June 23, 2023
|