Skip to content

(treatment) pathways produces some unanticipated values #779

Description

@mick-iqvia

We are looking at the behaviour of treatment pathways in order to implement a version running against a spark cluster.

There are a number of results that we are not sure are what was intended.

These are outlined in the image below, where 100, 200 etc are person ids.

pathwaysanomolies

The columns are:

  1. Input events - event cohorts - assume all these events fall within target
  2. Current output - these are current pathways
  3. Required output - these are the results we expected
  4. Henry has modified runPathways SQL and these are the outputs following his changes. He can comment on this.

I'll add the test data in a follow up comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions