-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ScoreCard 'Errors' #9
Comments
Thanks for the detailed report + questions! I look forward to digging in in Thanks, Josh On Fri, May 16, 2014 at 3:06 PM, Dapostol58 notifications@github.comwrote:
|
SummaryHi @Dapostol58, I've had some time to investigate -- overall we have:
Let me take your points in order...
I've take this opportunity to update the Scorecard to UMLS2014AA. But after investigating the file you shared with me, the problem wasn't actually with our UMLS version: the problem is your document had extraneous spaces in some code names. For example:
(Note the extra space before the close quotes in your codes: those shouldn't be there. Apologies for the superlatively unhelpful error messages :-))
This was indeed a bug. Now fixed -- thanks!
This is a valid LOINC code for sure -- and the Scorecard agrees with you on that point! It just happens not to be in the top 2000 most common LOINCs, so it gets flagged for review. (The reason for this behavior is we've seen many people use incorrect/obscure codes for common things like WBC, and we want to make sure that uncommon codes are chosen intentionally.)
I couldn't agree more about the clinical importance of recording subjective pain scale observations! On this point though, the value set called for in C-CDA is maintained (or rather... isn't actively maintained) by HITSP. This would be a good issue to raise on HL7's Structured Documents Working group mailing list: http://www.hl7.org/myhl7/managelistservs.cfm For now, my recommendation is to keep doing what you're doing and include pain scale observations with your vitals! You'll note that the Scorecard doesn't actually deduct any points for this -- it's just raising a flag to make sure you know what you're doing (which you do!). |
Two more notes: Since your "Results" is in fact a diagnostic imaging report, you may want to look at the "Findings" section which C-CDA uses specifically to convey the body of such reports: Also, there are lots of lab results embedded in free-text in your document. Ideally these would be coded as Results :-) |
I am sorry if this is not the correct forum, but I have some questions regarding the actual scoring results. While checking our newly created CCD code against the API we've received several messages that don't seem to make 'sense', per se.
In the 'General' category:
Your Results:
1 of 31 codes didn't match their displayName
Your code Preferred term What now?
SNOMED CT:173747005 "Roux-en-Y gastrojejunostomy" "Roux-en-Y gastrojejunostomy" See http://purl.bioontology.org/ontology/SNOMEDCT/173747005 - since our term matches theirs (exactly) we're presuming this is a 'bug'?
In the Lab Results category:
Your Results:
1 of 1 lab result codes weren't in the recommended value set
Note: This may be normal, if this C-CDA document includes unusual labs for which no common LOINC code exists. But look through the un-matched codes below to make sure you don't have a mapping error in your export pipeline.
Recommended value set:
LOINC Top 2000 Codes
Your code The issue What now?
LOINC:26380-6 "Hand-L XR 3V" Not in value set See http://purl.bioontology.org/ontology/LNC/26380-6 - again, is this a bug? This is a valid LOINC code
In the Vitals category:
Best Practice: Vitals in C-CDA should be coded with LOINC. Specifically, with codes from the HITSP Vital Sign Result value set.
Your Results:
5 of 47 vital sign codes weren't in the recommended value set
Note: This may be normal, if this C-CDA document includes unusual vitals for which no appropriate LOINC code exists. But look through the un-matched codes below to make sure you don't have a mapping error in your export pipeline.
Recommended value set:
HITSP Vital Sign Result
Your code The issue What now?
"Pain severity" Not in value set See http://purl.bioontology.org/ontology/LNC/38214-3
"Pain severity" Not in value set See http://purl.bioontology.org/ontology/LNC/38214-3
"Pain severity" Not in value set See http://purl.bioontology.org/ontology/LNC/38214-3
"Pain severity" Not in value set See http://purl.bioontology.org/ontology/LNC/38214-3
"Pain severity" Not in value set See http://purl.bioontology.org/ontology/LNC/38214-3
MOST healthcare facilities now consider Pain as the 'sixth vital sign' and are requesting that it be recorded in the same section. Are there any initiatives to do so?
Thank you,
Debra S. Apostol
The text was updated successfully, but these errors were encountered: