Create parseSearchParams Script

[cgolemme]

Summary

In this PR, I created a script to get the search parameters associated with each FHIR resource type.

New behavior

npm run build:search-parameters now creates a searchParameters.ts file that is a record of types mapped to all search parameters and their types associated with each resource type. This is accomplished by using the structure definitions to get the inheritance patterns for each resource, and then use the search-params.json to get the search parameters associated with each resource type. Specifically, this script looks at the base component of each search param in the search-parameters.json file and adds an object whose key is the name field of the search param and whose key is the code field for each resource type that appears in the base of each search param in search-parameters.json

Code changes

• README.md - updated the readme to reflect the change in behavior from this PR.
• src/data/searchParameters.ts - exports an object that has each resource type as keys and then search parameters and their types associated with each resource type as values.
• src/scripts/parseSearchParams.ts - script to create the object described above. Uses the structure definitions to get the inheritance patterns for each resource, and then uses the search-params.json to get the search parameters associated with each resource type.
• src/scripts/parseProperties.ts removed an unnecessary console.log I added in a previous PR

Testing guidance

• npm run check
• npm run build:search-parameters
• Look at the FHIR spec for a given resource and compare the search parameters listed there to the ones that are listed in the file searchParameters.ts. A good example to test is the Binary resource. Binary specifies no search parameters but inherits from Resource whose search parameters are shown here https://hl7.org/fhir/R4/resource.html#search. Compare this with BiologicallyDerivedProduct which also defines no search parameters but instead inherits from DomainResource (https://hl7.org/fhir/R4/domainResouce.html#search). BiologicallyDerivedProduct should have all search parameters of resource as well as the one search parameter that DomainResource has (_text)
• You can then check another resource that has search parameters defined and compare the file that the script creates to the spec. An example for this could be Condition. Here are the search params for that https://hl7.org/fhir/R4/Condition.html#search. Check that the ones listed match the file created, as well as the parameters that are inherited.

[elsaperelli]

Lgtm!