Stream: IG creation
Topic: Self-Instantiation in CapabilityStatement
Josh Mandel (Nov 10 2021 at 18:13):
US Core Server CapabilityStatement says:
"resourceType": "CapabilityStatement",
"id": "us-core-server",
"url": "http://hl7.org/fhir/us/core/CapabilityStatement/us-core-server",
"instantiates": [
"http://hl7.org/fhir/us/core/CapabilityStatement/us-core-server"
],
"_instantiates": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode": "SHALL"
}
]
}
],
Is this intended: the capability sstatement instantiates itself? (SHALL instantiate itself?)
Eric Haas (Nov 10 2021 at 20:15):
This is an expectation CapabitiiltyStatement and as such is kind of template too. I need to document how to turn it into an instance CapabilityStatement.
Eric Haas (Nov 10 2021 at 20:19):
It also drives testing.
Josh Mandel (Nov 10 2021 at 20:37):
Huh. I feel like this is just a way of tricking the tooling into spitting out the right webpage content, but maybe that's unfair?
Eric Haas (Nov 10 2021 at 21:17):
Request is from the product director himself. So I ran with it. CapabilityStatements are hard and cumbersome and this is bleeding edge stuff. I'm not sure all of it will survive
Eric Haas (Nov 10 2021 at 21:18):
Don't see anyone else using these elements
Grahame Grieve (Nov 10 2021 at 21:18):
me? What did I request?
Eric Haas (Nov 10 2021 at 21:26):
Applied: Mandate that CapabilityStatement.instantiates refer to US Core (FHIR#30889)
:point_down:
Grahame Grieve (Nov 10 2021 at 21:47):
well, I didn't request that the us core capability statement claim that it was instantiating itself, but that any server that implements US core be explicit about that in their capability statement
Last updated: Apr 12 2022 at 19:14 UTC
