Support validating against US Core

[awatson1978]

Is your feature request related to a problem? Please describe.
Support validation against US Core profile.
https://www.hl7.org/fhir/us/core/

Describe the solution you'd like
Using 'son-schema-resource-validation to validate against the US Core profile

Describe alternatives you've considered
Using ajv to do the validation.

Additional context
http://www.hl7.org/fhiR/profiling.html

[ElYusubov]

Hi @awatson1978 - Thanks for the contribution!
are you the only one, who maintains this interesting project?

QQ: I was checking demo page: https://node-on-fhir.meteorapp.com/fhir-query
There is no response to queries:

• http://hapi.fhir.org/baseDstu2/Patient?_count=10
  or http://hapi.fhir.org/baseR4/Patient?_count=10
  or http://hapi.fhir.org/baseR4/Patient/5
  am I doing something wrong :) ?

ps: i did not dig into the code yet... probably, i might miss something trivial here...

[awatson1978]

Good morning!
Yes, I'm the primary maintainer. This project is a recent refactor/rewrite of Meteor on FHIR, and was only published last month. So right now, it's mostly me.

We've had other contributors participate in the proceeding project Meteor on FHIR, and have taken the time to publish guidelines for Contributing and expected Code of Conduct to encourage participation and set appropriate expectations.

To your question about your demo page, if you inspect the browser console log you should find something like the following:

The issue is related to Cross-Origin Resource Sharing (CORS) and the fact that the public HAPI server we're fetching data from is running in a non-secure mode via normal HTTP, while your request is originating via HTTPS. If you go to the non-secure version of the demo page using regular HTTP, the queries should work:

http://node-on-fhir.meteorapp.com/fhir-query

This is something that is worth adding some user interface for. As I recall, we had a message in the Welcome screen that indicated whether the application was running in HIPAA compliant mode or not. Probably worth adding a tracking item for, but I'm not 100% sure I want to put it into the accounts system or require account creation to access that data. Might be better to put it in the public About or Info page.