Some LOINC codes that have no definition (e.g.: 81289-1) and there is some ambiguity as to its fit-for-purpose for a given implementation guide. Knowing who the requester/submitter was can help us to reach out and get some clarification, context, or potentially an addition for a definition for that term.
While Regenstrief will answer the technical knowledge source, may I interject as a user that answer lists often provide me more context. In this case it’s a preferred answer list from National Center for Biotechnology Information (NCBI) ClinVar. Perhaps injecting your possible use against that preferred answer list will help you realize if this is a fit or not?
Thanks for the quick reply. It was the answer list that introduced the ambiguity and questions for our working group and initiated this forum question. We weren’t able to determine whether the answer list should be changed or whether we needed a new LOINC code to request. A definition would provide more context on the intent.
I think the quickest route to your solution is to ask for an edit to a term. The mean submission time is currently 168 days. I didn’t want you to slowly gain answers to supportive information and only later decide a new term is needed.
At the bottom of the page at https://loinc.org/submissions/ , you’ll find “Request Changes to existing LOINC Content”. Have your full use case defined and demonstrate why the preferred answer list doesn’t fit. That nuance of an explanation will enable the Regenstrief team to reflect and either edit OR provide a new LOINC term for your use case. Get it in the queue sooner rather than later.
I think the quickest route to your solution is to ask for an edit to a term. The mean submission time is currently 168 days. I didn’t want you to slowly gain answers to supportive information and only later decide a new term is needed.
At the bottom of the page at https://loinc.org/submissions/ , you’ll find “Request Changes to existing LOINC Content”. Have your full use case defined and demonstrate why the preferred answer list doesn’t fit. That nuance of an explanation will enable the Regenstrief team to reflect and either edit OR provide a new LOINC term for your use case. Get it in the queue sooner rather than later.