Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SUSHI Config should support referring to profiles (and etc) by name/id #1018

Closed
cmoesel opened this issue Feb 10, 2022 · 0 comments · Fixed by #1091
Closed

SUSHI Config should support referring to profiles (and etc) by name/id #1018

cmoesel opened this issue Feb 10, 2022 · 0 comments · Fixed by #1091

Comments

@cmoesel
Copy link
Member

cmoesel commented Feb 10, 2022

There are bits of sushi-config.yaml that require the author to supply a full or partial URL referring to a resource in the IG. For example:

global:
  Patient: http://example.org/fhir/StructureDefinition/my-patient-profile
  Encounter: http://example.org/fhir/StructureDefinition/my-encounter-profile

resources:
  Patient/my-example-patient:
    name: My Example Patient
    description: An example Patient
    exampleBoolean: true
  Patient/bad-example: omit

groups:
  GroupA:
    name: Group A
    description: The Alpha Group
    resources:
    - StructureDefinition/animal-patient
    - StructureDefinition/arm-procedure
  GroupB:
    name: Group B
    description: The Beta Group
    resources:
    - StructureDefinition/bark-control
    - StructureDefinition/bee-sting

It would be more user-friendly if SUSHI allowed you to use the resource names (or ids) as you have defined them in the IG. If this was allowed, then the examples above might look like this:

global:
  Patient: MyPatientProfile
  Encounter: MyEncounterProfile

resources:
  my-example-patient:
    name: My Example Patient
    description: An example Patient
    exampleBoolean: true
  bad-example: omit

groups:
  GroupA:
    name: Group A
    description: The Alpha Group
    resources:
    - AnimalPatient
    - ArmProcedure
  GroupB:
    name: Group B
    description: The Beta Group
    resources:
    - BarkControl
    - BeeSting

Of course, the names should be uniquely identifiable. If a name used could resolve to more than one thing in the IG, then the more complete form would need to be used.

cmoesel added a commit that referenced this issue May 18, 2022
Allow authors to use resource names or ids for:
- global profile values (previous required canonical)
- group resources (previously required relative URL)
- resources (previously required relative URL)
- resources exampleCanonicals (previously required canonical)

Fixes #1018
julianxcarter pushed a commit that referenced this issue May 24, 2022
* Support for using resource names/ids in sushi-config.yaml

Allow authors to use resource names or ids for:
- global profile values (previous required canonical)
- group resources (previously required relative URL)
- resources (previously required relative URL)
- resources exampleCanonicals (previously required canonical)

Fixes #1018

* Support config groups with no resources

Fixes #1019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant