Giter Club home page Giter Club logo

cdx's People

Contributors

anthonyoleary avatar asterite avatar bcardiff avatar bolom avatar dependabot[bot] avatar devduarte avatar diegoliberman avatar flbulgarelli avatar ftarulla avatar ggiraldez avatar juanboca avatar juanedi avatar leandroradusky avatar lmatayoshi avatar macoca avatar matiasgarciaisaia avatar mmuller avatar nthiad avatar omelao avatar spalladino avatar straight-shoota avatar tripledub avatar waffle-iron avatar waj avatar ysbaddaden avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

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

Forkers

devwaker tripledub waj matiasgarciaisaia digideskio nthiad radxrad

cdx's Issues

Implement permission model

Users have certain permissions. A subset of those permission can be granted to applications through the create of an API Auth token.

Permissions are defined by the intersection of the following:

  1. Access to the devices under a node and it's subnodes in the location hierarchy.

  2. Access to the devices under a list of institutions

  3. Access to results aggregated by one or more of the following dimensions:

    a) Date: aggregate by day/week/month/year.

    b) Location

    c) Demographics: sex, age ranges

  4. Access to results between a defined static or dynamic periods: "between Jan 1st and Feb 28th" or "between 1 year ago and 1 month ago".

  5. Access to a subset of the fields

Group by date ranges

A Querystring or JSON Query should support the following aggregate functions and display the count for each of the correspondent date ranges:

year(date) -> '2014'

month(date) -> '2014-03'

week(date)-> '2014-W45'

day(date) -> '2014-03-01'

[permission] By Resource

Support the following:

{ 
  "statement":  [ 
    { 
      "effect":"allow",
      "action": ["readInstitution", "updateInstitution"],
      "resource": "cdxp:institution/1"
    }
  ],
  "delegable": true
}

Determine Result location

If reporting device can only be used in one laboratory, use laboratory location. If device can be used in more than 1 laboratory, then the result needs to be posted specifying laboratory or location can't be determined.

[permissions] Implicit

Support the following:

{
  "statement": [
    {
      "effect":"allow",
      "action": "*",
      "resource": "*",
      "condition": {"is_owner" : true}
    }
  ],
  "delegable": true
}

This policy is granted automatically to each user that signs up.

Design a way to describe the different types of data inside the report.

These are:

  1. Sensitive data, such as patient ID, name, age, phone number, SSN, that should be encrypted.

  2. Demographic data, useful to search for later and for analytics, such as gender, ethnicity, age range. They could have a predefined set of values or be an open field.

  3. QA Data, such as assay/cartridge ID.

  4. All the rest.

Design manifest format

  • Manifest can be manufacturer provided (and therefore signed) or user defined.
  • Support different source formats (only JSON for now)
  • See Field mapping strategy diagram (to be attached)
  • Allow field renaming
  • Allow content rewriting/curation
  • Manifest can contain a version

[permission] Superadmin

Support this permission policy:

{
  "statement": [
    {
      "effect": "allow",
      "action": "*",
      "resource": "*"
    }
  ],
  "delegable": true
}

This sort of policy would be given after server provisioning by running a rake task.

[permission] Not delegable

Support the following:

{ 
  "statement": [ 
    { 
      "effect":"allow",
      "action": ["readInstitution", "updateInstitution"], 
      "resource": "cdxp:institution/1"
    }
  ], 
  "delegable": false
}

This should keep a user from delegating this permissions to others.

Multiple Results per Assay

  • Each event can report the results of more than one condition.
  • Each condition has a name or description (this could be nomenclated).
  • The event contains one result for each condition that the Assay tests, for that particular instance of the test.
  • API should allow grouping by condition, filtering by result, etc.

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.