Stream: IG creation
Topic: Using the HL7 vital signs profile in an IG
Vassil Peytchev (Oct 28 2021 at 20:59):
For a given Implementation guide, I want to indicate that it includes support for the HL7 vital signs profile (without any changes).
According to http://hl7.org/fhir/R4/vitalsigns.html the canonical URI is http://hl7.org/fhir/StructureDefinition/vitalsigns (which then resolves to http://hl7.org/fhir/R4/vitalsigns.html)
If the above is correct, what do I need to do to add this profile to the IG? I tried adding it to the Capbilitystatement and to the ImplementationGuide Resource but got an error.
Load Reference[http://hl7.org/fhir/StructureDefinition/vitalsigns] (00:14.0436)
Publishing Content Failed: Bad Resource Identity - should have the format [Type]/[id] where Type is a valid resource type:http://hl7.org/fhir/StructureDefinition/vitalsigns
Any suggestions?
John Moehrke (Oct 28 2021 at 21:10):
that worked for me
John Moehrke (Oct 28 2021 at 21:11):
Ill try a fresh build on my IG
John Moehrke (Oct 28 2021 at 21:15):
my build works
Vassil Peytchev (Oct 28 2021 at 22:14):
Where do I place the parent? In the Implementation Guide or in the capability statement?
John Moehrke (Oct 29 2021 at 11:36):
The implementationGuide does not need to say anything, as these are in the core FHIR spec. So you just use that profile canonical rather than a resource.
John Moehrke (Oct 29 2021 at 11:38):
John Moehrke said:
that worked for me
this was in my FSH for a profile I was doing derived off of vitalsigns.
John Moehrke (Oct 29 2021 at 11:41):
I see you want "without any change" .... thus you would simply put this vitalsigns canonical URI in the IG CapabilityStatement (Requirements) as another .rest.resource.profile. (along with all the other resources you want a server to implement)
John Moehrke (Oct 29 2021 at 11:42):
given that CapabilityStatement doesn't have much of an automatic rendering by the IG builder, I unusually just state these in narrative on either the -info page or description element.
Last updated: Apr 12 2022 at 19:14 UTC
