Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Joaquin
    @joaquinrcsi
    Hi all! I've a question. I've been using Ripple with Marand but is not working anymore. Has anyone here set up Ripple using just EtherCIS server?
    Tony Shannon
    @tony-shannon
    Hi @joaquinrcsi I understand you are working with Derek at RCSI.. he will have mentioned our resources are v tight just now, (open source has a working for free problem you may be aware of) but I'll guide as best I can, as RCSI have been supportive in the past
    would be useful to know your tech skills
    Tony Shannon
    @tony-shannon
    you should be aware of this work here
    the key aspect of the stack you need is the qewd courier aspect which is Docker based
    so if you are versed in Docker, please take a look at setting this up
    as its the key part of the Ripple stack that interacts with PulseTile and EtherCIS
    @anon100 you should be trying the same tactic for now.. again not sure of your tech skills tbh
    Joaquin
    @joaquinrcsi
    @tony-shannon , thank you for your help. I'm a developer working mostly with the Javascript stack but I'm helping my team to set this up. We're running Ripple on a digital ocean box so basically what we need is just to set EtherCIS up. I tried the Docker's version of the server + db but apparently that version is not updated and we're having problems to get results from the server. As I said the middleware is already running so we were thinking about starting the QEWD server and change the server.js file pointing to the new one.
    Tony Shannon
    @tony-shannon
    ok @joaquinrcsi there are several issues there and you need to break them out..
    Aside from the EtherCIS issue you mention (Suggest you park just now) have you tried to install the docker based version of Qewd-Courier as I suggested above?
    https://github.com/QEWD-Courier/QEWD-Courier
    As our funding is limited at this time, we cannot maintain earlier versions of our stack, so suggest you move towards the latest version, and Qewd-Courier is probably the best place to start
    Joaquin
    @joaquinrcsi
    @tony-shannon I'll try that version now. Thank you!
    Joaquin
    @joaquinrcsi
    Hi all! I tried installing the Docker version of the QEWD- Courier and I got this error:
    image.png
    Dmitry Solyannik
    @DmitrySolyannik
    Hello @joaquinrcsi , this problem relates to wrong path to helm folder or to yottadb folder. Please recheck it one more time carefully.
    And also one thing if you did docker pull for latest changes. You should change yottadb version from 1.22 to 1.24
    Here is example: sudo docker run -it --name orchestrator --rm --net qewd-net -p 8080:8080 -v ~/qewd-courier/helm:/opt/qewd/mapped -v ~/qewd-courier/yottadb/orchestrator:/root/.yottadb/r1.24_x86_64/g rtweed/qewd-server
    Joaquin
    @joaquinrcsi
    Thank you very much @DmitrySolyannik I'll check that now.
    Joaquin
    @joaquinrcsi
    Hi @tony-shannon I set everything up but when I'm trying to log in into the QEWD Management Password says that the password is incorrect. Do you know why it could be happening?
    Tony Shannon
    @tony-shannon
    @joaquinrcsi can you send a screenshot please? what url are u on?
    & what are u trying to do /what have you been able to do /where did you get stuck
    Joaquin
    @joaquinrcsi
    image.png
    We have been attempting to install the latest version of QEWD-Courier using dockerised QEWD and our own local ethercis database. The ethercis db is working and we are able to query it and similarly we can access qewd-monitor on the dockerised QEWD. Despite this, we are having issues with running the Microservices. With our ethercis db, orchestrator, auth, oidc, openehr services running and attempting to access the helm index, we receive an error message stating that the auth_service cannot retrieve "getRedirectUrl" of undefined as it shows in the image below (also the call to http://localhost:8080/api/initialise doesn't get any response) :
    image.png
    image.png
    image.png
    Moreover, we have also attempted to set up the older version of QEWD-Courier available at Dmitry's repository and when running all the microservices, we are met with an error suggesting that the auth microservice has been shut down. This was only attempted to try to set up a verified build of the project so solving this is less important.
    image.png
    Dmitry Solyannik
    @DmitrySolyannik
    Hello @joaquinrcsi , could you please change http://localhost to your private IP address ? e.g. http://192.168.**.** in global_config.json and in oidc configurations too.
    Also regarding getRedirectUrl error, please check install_modules.json and line with openid-client should be with version. e.g. openid-client@2.5.0
    Also remove all node_modules and package-lock.json
    P.S. orchestrator install this modules itself, so you can start orchestrator alone very first time, it will install all needed modules and then you can start all ms together
    Tony Shannon
    @tony-shannon
    thanks @DmitrySolyannik , hope that helps @joaquinrcsi
    Joaquin
    @joaquinrcsi
    @DmitrySolyannik @tony-shannon Thank you very much for your help! The project is now up and running (openid-client version was the key) so hopefully now we can start the real development now and won't be asking any more silly questions! Thank you again.
    Tony Shannon
    @tony-shannon
    Glad to hear it @joaquinrcsi . PS if you need help with EtherCIS test data Dmitry can give you an update on test data seeder
    Joaquin
    @joaquinrcsi
    Thank you very much! Actually I think we're gonna need it soon.
    kevinoflanagan
    @kevinoflanagan
    image.png

    Hi guys,

    I am currently working on an instance of qewd-courier using a dockerised ethercis (the one above that joaquin mentioned previously when we were having setup issues!)

    When attempting to add clinical content I am met with a 400 error as per above but not sure exactly where I'm going wrong

    I'd greatly appreciate any help with this as I suspect I've missed a step in the templates for the ethercis db
    Tony Shannon
    @tony-shannon
    Hi @kevinoflanagan , thats an EtherCIS related issue but I don't recognise it, can u add more detail as to what steps you have taken & where this error is showing up
    kevinoflanagan
    @kevinoflanagan
    Hi @tony-shannon . I have set up QEWD-Courier microservices: orchestrator, oidc, openehr_service, auth_service and have both ethercis-server_1 and ethercis_db_1 created as per the below docker-compose.yml file. The error appears when attempting to add a new "Top 3 Things" instance within the PulseTile interface. Any other GET query for medications, diagnoses etc results in a 200 response so all seems fine there but this error appears on creation. For reference I do not have the DDS microservice running as we do not have access to the DDS service and am in the process of using a local implementation for that (As an aside I am attempting to use the FHIR-MPI microservice as an alternative for this). It may just be the case I have overlooked a step here in ignorance.
    image.png
    Ian McNicoll
    @freshehr
    @kevinoflanagan - can you post the json composition that you were trying to save here?
    ah - or are you just trying to do a GET on the existing data?
    Ian McNicoll
    @freshehr
    Have you added any data to Top 3 herading yourself or are you just using whatever was setup there by default?
    kevinoflanagan
    @kevinoflanagan
    Hi all apologies for the delayed response. I subsequently updated to the latest version of the etherCIS release and qewd microservices with all working fine now so not entirely sure where I went wrong before but seems to be resolved. Thank you for the help!
    Tony Shannon
    @tony-shannon
    glad to hear that @kevinoflanagan
    VirtualPM
    @VirtualPM
    I noticed the showcase stack is offline at showcase.ripple.foundation . Are there plans to bring it back online?
    PhilBarrett
    @PhilBarrett
    Hi @VirtualPM we've been busy refactoring PulseTile onto React-Admin (https://github.com/marmelab/react-admin) see https://youtu.be/wZZKO6ae3h4 for progress to date
    VirtualPM
    @VirtualPM
    @PhilBarrett I did see the videos posted on YouTube. Looks good. Will you be sharing more information on how you are using Node-RED? It looks like it has interesting capabilities for device and instrument integration.
    Tony Shannon
    @tony-shannon
    Hi @VirtualPM check this work out https://github.com/RippleOSI/RFShowcase-NodeRed-Redis-v1 Our instinct is that QewdJS and NodeRed could work very well together