You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-profileEncounter: http://example.org/fhir/StructureDefinition/my-encounter-profileresources:
Patient/my-example-patient:
name: My Example Patientdescription: An example PatientexampleBoolean: truePatient/bad-example: omitgroups:
GroupA:
name: Group Adescription: The Alpha Groupresources:
- StructureDefinition/animal-patient
- StructureDefinition/arm-procedureGroupB:
name: Group Bdescription: The Beta Groupresources:
- 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: MyPatientProfileEncounter: MyEncounterProfileresources:
my-example-patient:
name: My Example Patientdescription: An example PatientexampleBoolean: truebad-example: omitgroups:
GroupA:
name: Group Adescription: The Alpha Groupresources:
- AnimalPatient
- ArmProcedureGroupB:
name: Group Bdescription: The Beta Groupresources:
- 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.
The text was updated successfully, but these errors were encountered:
* 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
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: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:
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.
The text was updated successfully, but these errors were encountered: