Support specifying clinicalSiteSystem in configuration file #99
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
clinicalSiteSystem can now be specified in the config file, similar to how clinicalSiteID is, except clinicalSiteSystem is optional
New behavior
If a
clinicalSiteSystemis added to theconstructorArgsofCSVClinicalTrialInformationExtractorin the config file, that value will be used for thesystemfield of the site object in the ResearchStudy resource. If no system is specified, thesystemfield will be omitted in the output.Code changes
CSVClinicalTrialInformationExtractor.jsnow takes an optionalclinicalSiteSystemconstructor argument and adds that to the formatted data for the Research StudyResearchStudyTemplate.jsnow takes an input forclinicalSiteSysteminstead of just using an example.com valueCSVClinicalTrialInformationExtractor.test.jsandresearchStudy.test.jshave been updated to reflect the above changesTesting guidance
clinicalSiteSystemto the constructor arguments of theCSVClinicalTrialInformationExtractorand see that the correct value appears in the output and that there is no system in the output if the argument is removed from the config