Location resource has a search parameter called name whose target can be Location.name or Location.alias.
Is it possible to achieve this using fhir-qb?

Possible feature request, how about a config like this?

    name: {
        type: 'string',
        fhirtype: 'string',
        xpath: 'Resource.name, Resource.alias'
    },

Thanks!

Please consider adding your resource generator (ref: bluehalo/fhir-facade-starter#9 (comment)) to this repository as an additional package.

It would be helpful when we create/use custom profiles (custom StructureDefinitions) to be able to add them to our fhir server implementation.

👋 Hi team members, contributors, and wonderful developers!

This repository started as a way to publish several packages that are primarily used by node-fhir-server-core, a core library for building FHIR servers. In an effort to collect all publisher packages together, we will be moving these packages into node-fhir-server-core and converting that repository into a monorepo.

But why?
Having everyone in one place will improve developer experience, issue tracking, and package quality. Read more about it here.

Thanks!

As mentioned in the title, qb.buildSearchQuery(req, configs) is giving incorrect query for :missing modifier. Test-cases too have incorrect expectations.
https://github.com/Asymmetrik/phx-tools/blob/master/packages/fhir-qb/index.test.js#L2505

Seems like a silly bug?

Version:
"@asymmetrik/fhir-qb": "^0.10.2"

Version:
"@asymmetrik/fhir-qb": "^0.10.3"

It seems like buildSearchQuery(req, configs) fails/aborts when req has an unknown(not defined in configs) parameter. Side effect of this is that it fails all the times for express req object as express req.params contains base_version parameter which is of no interest for mongo query and hence not defined in configs.

Isn't it more convenient/usable if fhir-qb ignores undefined params?

Thanks!

This repo was uploaded today(12/18/18). We need to publish all these packages except for fhir-sanitize-param by 12/20/18.

Recommend copying the "Getting setup" section from the CONTRIBUTING.md into the README.md.

I started out with npm install followed by npm run bootstrap resulting in various issues. Knowing the contents of the "Getting setup" section from the CONTRIBUTING.md upfront would have been very helpful.

For Typescript developers, it would be very helpful if you contribute the type definitions for each of the packages to DefinitelyTyped (https://definitelytyped.org).