Skip to content

Error when expanding task-code ValueSet resource #4971

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

Closed
volodymyr-korzh opened this issue Jun 8, 2023 · 0 comments · Fixed by #4974
Closed

Error when expanding task-code ValueSet resource #4971

volodymyr-korzh opened this issue Jun 8, 2023 · 0 comments · Fixed by #4974
Assignees

Comments

@volodymyr-korzh
Copy link
Collaborator

Expanding task-code ValueSet after pre-expansion returns NullPointerException

To Reproduce

  1. Start with a default implementation.
  2. In Persistence module configuration and set the configurations to YES:
  • Seed Base Validation Resources
  • Lucene Indexing Enabled
  • Enable Terminology Index
  1. Save the updated configuration settings and restart the Persistence module.

  2. Once the Persistence module has finished restarting (this may take several minutes), wait at least an additional 15 minutes to allow time for all ValueSet pre-expansions to complete.

  3. Query that a ValueSet exists for http://hl7.org/fhir/ValueSet/task-code using a REST GET or browser e.g.:
    http://localhost:8000/ValueSet/?url=http://hl7.org/fhir/ValueSet/task-code

  4. Request $expand operation on the same ValueSet using a REST GET or browser e.g.:
    http://localhost:8000/ValueSet/$expand/?url=http://hl7.org/fhir/ValueSet/task-code

Expected Behaviour:

Should return the expanded ValueSet.

Actual Behaviour:

Returns an OperationOutcome similar to:

{
  "resourceType": "OperationOutcome",
  "issue": [ {
    "severity": "error",
    "code": "processing",
    "diagnostics": "Failed to call access method: java.lang.NullPointerException"
  } ]
}
@volodymyr-korzh volodymyr-korzh self-assigned this Jun 8, 2023
@volodymyr-korzh volodymyr-korzh linked a pull request Jun 9, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant