cqframework / cqframework/clinical-reasoning
Error encountered while generating CCDA release
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 43
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 13
Description
We get an error when attempting to $release the CCDA package:
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "HAPI-0389: Failed to call access method: org.springframework.dao.InvalidDataAccessApiUsageException: HAPI-1764: theKey must not be null or empty"
}
]
}
Attempting to $release https://github.com/cqframework/vsp-ig/blob/master/input/resources/library/Library-ccda-vsp-3-0-0-draft.json
The issue seems to be that HAPI can’t persist the v3-RoleClass CodeSystem.
It throw on this call to setKey because the value being passed in is null.
I believe the missing value corresponds to the property for the “EXLOC” code - the definition is here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the CCDA release using Library-ccda-vsp-3-0-0-draft.json, then inspect the linked TermReadSvcImpl.java call around line 3460. Compare the v3-RoleClass CodeSystem definition with the EXLOC property and trace the null key reported by HAPI. Done means the CCDA package releases without the HAPI-1764 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100