|
About the loinc-implementation category
|
|
0
|
96
|
June 23, 2023
|
|
COVID and Prerelease pages inconsistent
|
|
3
|
104
|
January 12, 2022
|
|
LOINC Maintenance in Cerner
|
|
3
|
161
|
December 6, 2021
|
|
LOINC Implementation Helpful Suggestions
|
|
5
|
177
|
January 19, 2021
|
|
LOINC Answer Lists independent use
|
|
0
|
138
|
November 5, 2018
|
|
Data missing between versions.
|
|
2
|
157
|
September 12, 2018
|
|
LOINC table file database engine
|
|
0
|
115
|
February 26, 2018
|
|
Choosing between using on outside vendor to do mapping versus doing it yourself
|
|
1
|
136
|
August 6, 2017
|
|
Answer Lists
|
|
1
|
119
|
July 6, 2017
|
|
What to do with map to file
|
|
2
|
133
|
March 14, 2017
|
|
Sending textual comments
|
|
1
|
165
|
August 16, 2016
|
|
Inconsistencies in LinguisticVariants format
|
|
4
|
134
|
February 1, 2016
|
|
UCUM composition
|
|
0
|
117
|
October 23, 2015
|
|
Using LOINC to link results from labs
|
|
2
|
117
|
October 27, 2014
|
|
CSV structure for copyrights
|
|
0
|
102
|
September 18, 2014
|
|
LOINC implementation for Genetic Cancer Labs
|
|
1
|
105
|
October 1, 2013
|
|
LOINC database and multi-axial hierarchy out of sync?
|
|
2
|
173
|
May 9, 2013
|
|
Jumping Off
|
|
1
|
117
|
January 11, 2013
|
|
LOINC database and multi-axial hierarchy out of sync?
|
|
0
|
135
|
October 7, 2010
|
|
Short Name vs. all components in HL7
|
|
1
|
136
|
August 23, 2010
|
|
Best practice for maintaining multiple versions?
|
|
2
|
111
|
April 16, 2009
|
|
LOINC Adopters Directory on loinc.org
|
|
0
|
106
|
July 26, 2008
|
