Adverse Event context additions #178
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds two new utility functions,
getAdverseEventsFromContextandgetAdverseEventEntriesFromContext.New behavior
contextUtilsmake it possible to fetch AdverseEvent resources in the context bundle.FHIRAdverseEventExtractorwill now only throw an error if astudyis not included in its contructorArgs. Previously, an error would be thrown whenever there were noResearchStudyresources found in context, even though it's not exactly necessary if astudyis included.Code changes
contextUtils.js.getResearchStudiesFromContextare now logged as debug messages inFHIRAdverseEventExtractor.js, which a custom error being thrown by that Extractor if thestudycontructorArg isn't included either.Testing guidance
Testing guidance will be included in the corresponding E-MEF PR.