Skip to content

Using meta.profile to determine which profile to validate against #3

Description

@arscan

Since meta.profile is optional (unless this is mentioned within the narrative in the IG), it might be a good idea to consider choosing which profile to validate for Observation resources based on the Observation.code which are set to fixed values for each of the profiles.

if type_identifier.include?("sexual-orientation")

I understand this is a somewhat complex topic though. Having the server communicate the intended profile explicitly makes testing easier. But also it might be less realistic, or encourage a requirement (using meta.profile) that doesn't exist.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions