clinical-meteor / node-on-fhir Goto Github PK

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

Is your feature request related to a problem? Please describe.
https://github.com/fhircast/sandbox.js

Describe the solution you'd like
Migrate the subscription service libraries.

Describe alternatives you've considered
DDP - deprecated.
Websubhubub - deprecated.

Describe the deprecation
Please provide a clear and concise description of what library has been deprecated.

The Error Message
The following error message was emcounted:

warning [email protected]: simple-oauth2 v2 is no longer supported. Please upgrade to v3 for further support
warning simple-oauth2 > [email protected]: This module has moved and is now available at @hapi/wreck. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning simple-oauth2 > wreck > [email protected]: This module has moved and is now available at @hapi/bourne. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning simple-oauth2 > [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning simple-oauth2 > joi > [email protected]: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning simple-oauth2 > wreck > [email protected]: This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning simple-oauth2 > wreck > [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning simple-oauth2 > joi > [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning simple-oauth2 > joi > topo > [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
warning simple-oauth2 > wreck > boom > [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

To Reproduce
Steps to reproduce the behavior:

3. Any custom packages or plugins you may be using.

symptomatic:vault-server

4. Identify the build pipeline(s) used when producing the error.

yarn-install

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: yarn

Additional context
Add any other context about the problem here.

Meteor v3 (beta) has been released. Time to migrate to await/async across entire application.

Don't need to use master/slave language.

User should be able to delete user account. Will need distributed remove() function across the data lake.

Issue created in response to discussion in #22.

The predecessor project Meteor on FHIR eventually evolved towards including an AppInfoPage that included the About the Business card along with some environmental config info.

We need to display environmental configs, so people understand in what state the app is running.

Must Haves

• Meteor Accounts User ID
• Connected Status
• NODE Environment
• Meteor Base URL
• Git Release Version
• Git Branch
• Git Commit

Under Consideration

• HTTP Protocol
• Browser Timezone
• Server Timezone
• System Status

Any others?

Library Source
The library or source file where the dependency issues is occuring.

[email protected]:

Dependency
A clear and concise description of what the dependency that needs updating.

mongoose "~3.6.18" needs to be updated to 5.9.27
this will require forking and maintaining a copy of https://github.com/jon49/json-schema-to-mongoose

Is your feature request related to a problem? Please describe.
r4 and r5 JSONSchema libraries should be included in main boilerplate.

Describe the solution you'd like
Will need JSONSchema to SimpleSchema parsing.

Need an expiration date for when an invitation code expires, so it doesn't persist indefinitely.

// server/AccountServer.js
if(get(Meteor, 'settings.private.invitationCode')){
  if(moment().now() < get(Meteor, 'settings.private.invitationExpirationDate')){
    // do some stuff
  } 
}

main and development should require pull requests, and not allow force pushing or deletion.

Is your feature request related to a problem? Please describe.
Validation against custom profiles.

Describe the solution you'd like
Use json-schema-resource-validation to validate against custom profiles.

Describe alternatives you've considered
Using ajv to validate.

Additional context
http://www.hl7.org/fhiR/profiling.html
https://www.hl7.org/fhir/us/core/

Tracking issue for:

• https://github.com/clinical-meteor/node-on-fhir/security/code-scanning/7

These .pem files were for testing and sandbox usage only, but are causing warnings and not a best practice. Need to remove and rebase.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Run with meteor --settings config/settings.nodeonfhir.json
Receive the following errors:

[[[[[ /usr/src/app ]]]]]

=> Started proxy.
=> Meteor 2.10.0 is available. Update this project with 'meteor update'.
=> Errors prevented startup:

   While selecting package versions:
   error: unknown package in top-level dependencies:
   mitre:space-health-registry
   unknown package in top-level dependencies: mitre:consent-engine

=> Your application has errors. Waiting for file change.

Additional context
Running in Docker using the following Dockerfile:

FROM node:14.20

ARG config="configs/settings.nodeonfhir.json"
ARG user=meteor
ARG group=meteor
ARG uid=1001
ARG gid=1001

ENV ROOT_URL="http://localhost:3000"
ENV NODE_ENV="test"

RUN curl "https://install.meteor.com/" | sh

COPY . /usr/src/app
WORKDIR /usr/src/app

RUN groupadd -g ${gid} ${group}
RUN useradd -u ${uid} -g ${group} -s /bin/sh -m ${user}
RUN chown -Rh ${uid} /usr/src/app
RUN chmod -R 700 /usr/src/app

USER ${uid}:${gid}

RUN meteor npm install

EXPOSE 3000
CMD ["meteor", "--settings", "${config}"]

Describe the deprecation
Babel presets still being used in material-fhir-ui. Need to update that build pipeline.

The Error Message
The following error message was emcounted:

warning material-fhir-ui > [email protected]: We're super 😸  excited that you're trying to use ES2017+ syntax, but instead of making more yearly presets 😭 , Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user 😎 ! We are also in the process of releasing v7, so please give http://babeljs.io/blog/2017/09/12/planning-for-7.0 a read and help test it out in beta! Thanks so much for using Babel 🙏, please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel
warning material-fhir-ui > babel-preset-latest > [email protected]: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
warning material-fhir-ui > babel-preset-latest > [email protected]: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!

To Reproduce
Steps to reproduce the behavior:

3. Any custom packages or plugins you may be using.

material-fhir-ui

4. Identify the build pipeline(s) used when producing the error.

yarn install