Git Product home page Git Product logo

cql-exec-vsac's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

cql-exec-vsac's Issues

Feature request to allow the additional processing of valuesets as they are returned

Hey @cmoesel hope you don't mind entertaining another requirement we have. I would like to see if we could fit it into this library in a non-obtrusive way. If you think this is beyond the goals of this library that is ok. I will also implement it, if we can agree on a solution.

We have a requirement where either locally loaded valuesets, or externally loaded valuesets, in certain scenarios when the valueset might contain a code with a specific system, such as a CPT code, we also want to map that same code to a HCPCS code, if that same code exists in both valuesets.

We do not want to modify the external data we are processing and include both codes and valuesets and we would like to avoid modify the CQL as well.

I am wondering if there is a way we could fit it in here. I have a couple ideas that might open things up to other features in the future as well.

  1. When calling ensureValueSets* functions, as part of our new options object we could include a callback function that would optionally be called after we download the valueset and when we are looping through the codes. This callback would accept { code, service, version } and optionally return an array of additional codes that might need to be added. This has the benefit of being handled when we are already looping through the codes. The negative here is that we could only really add additional codes or do nothing (unless we came up with a more complicated return signature for this callback function).
  2. Add a final callback, after we download the valueset but before we create the Code and Valueset objects that would optionally be called that would pass in the entire list of codes that were downloaded from that valueset as a pure function with a return signature of an array of codes. This would allow the caller to modify the list however they wanted and then return a new list. The benefit here is that it is a bit more robust for anyones needs, the downside would be potentially having to loop through the array of codes again, depending on the need of the user.

Also open to other ideas or any thoughts you have.

Thank you!

Is there a reason we map specific code systems from oid to uri?

Specifically looking at src/svs.js line 60-73, if we a code system from the list in this repo, we update the system to be the uri instead of the oid? Is there a functional reason for this?

Is it possible to include both? Keep the urn:oid and also add the uri side by side?

We have cases where we are receiving the codes as the urn:oid and I would rather not update the source data.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.