Skip to content

automatic validation on FHIR Document #355

@oliveregger

Description

@oliveregger
  1. FHIR documents are defined by a FHIR Bundle and containing as the first entry a FHIR Composition
  2. The FHIR composition is characterized by a categories 0..* and type 1..1 a) The derived profile defines directly one or more categories and/or type CH VACD
    b) The derived profile requires a conformsTo to another Composition which defines category / type (e.g. CH IPS
  3. We would like to have a universal profile which would validate against all doczument profiles which would be applicable
    a) how do return mutliple profile validation results (till now there is an OperationOutcome for one profile) - 1) one issue per validation/profile and maybe details inside or 2) Use TestReport instead of OperationOutcome (would need to adapt the $validate Operation)
    b) how can we track the relationship between category / type and document profiles

how can we track the relationship between category / type and document profiles with profiles

  1. could we create a custom hapi-fhir resource?
    ql: no search parameters, no index, stored as blobs? need to analzye
  2. creating an own table in hapi-fhir db? use it via spring-data repository? e.g. extend like https://github.com/ahdis/matchbox/blob/main/matchbox-server/src/main/java/ca/uhn/fhir/jpa/model/entity/NpmPackageVersionResourceEntity.java#L55

tasks which updates the table for each upload/modification of an IG

  • serach for all Bundle profiles which are documents in an ig
  • retrieve the Composition profile
  • from the composition profile retrieve the category/type codings (could be simplified 1 and 1), check conformsTo

define a profile url which would invoke "http://matchbox.health/validate/document"

simple mode: just one profile fits -> return standard operation outcome

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