[Xavier Gansel]

Hi Tim,

Our use case is that we aim at automating LIVD files production (today 100% manual creation). To do so, we plan to retrieve LOINC code breakdown into parts from your FHIR resource rather than copy/paste them from RELMA / search.loinc.org details pages 😉

LIVD files may be re-published following the ‘max-90-days’ LOINC code check rule after each LOINC release. This LIVD re-publication will depend on the impacts of the code modification(s) we may detect. From 3y historical background (our 1st LIVD is 3y old) all possible situations were detected (no code modification, minor part update, code deprecation, new product release from us).

Consequently we may need data not only from the current LOINC release but potentially past one (i.e. retrieve LOINC codes according to a given LOINC release version) ; this is still under analysis and specification at our level.

To concur with @cesharp, note that a service-level agreement would be more than beneficial. As you will understand it is challenging to rely on an ‘unsecure’ resource to produce LIVD files flying to the lab market.

Hope this helps.
Xavier

• This reply was modified 6 months, 1 week ago by Xavier Gansel.

[Xavier Gansel]

Hi Tim,

Can we access a LOINC code breakdown into parts according to one particular version ?

say I want the part for a code in 2.59?

thanks,

Xavier

• This reply was modified 6 months, 2 weeks ago by Xavier Gansel.

[Xavier Gansel]

Tim,

Although being a beta release, what are your plan to upgrade this server to a stable release ?

To which extend can we develop some thing querying your FHIR resource that will then be used on the long range and go to some production space ?

thanks,

Xavier

[Author]

Posts