Skip to content

Consider fixed value for single-option code filters #24

Description

@eyuasa

Currently, all code filters get placed in narrative tables. however, there are some situations where there are constraints on elements like status (e.g., Encounter.status = completed on the BMI screening measure (CMS69: PCSBMIScreenAndFollowUpFHIR)). Should these be represented as fixed code values instead? Probably would happen very rarely because the code filter would need to apply to all instances of the profile used by all measures. This may need to be moved forward here or to an upstream measure development process.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions