Generated Narrative: OperationDefinition crmi-publish

URL: [base]/$publish

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INbundle1..1Bundle (CRMI Publishable Bundle)

The publishable bundle to be processed. The bundle must conform to the CRMIPublishableBundle profile, meaning:

  • Bundle type must be 'transaction'
  • First entry must contain an ImplementationGuide resource
  • All entries must have proper transaction request information

The bundle contains all related artifacts that should be published as an atomic unit.

OUTreturn1..1Bundle

The bundle transaction response containing the results of processing each entry in the input bundle.

Each entry in the response bundle corresponds to an entry in the input bundle and contains:

  • The HTTP status code for the transaction
  • The location of the created/updated resource (if successful)
  • Any operation outcomes or error messages

The response follows the same structure as the core FHIR Bundle transaction response.

The CRMI publish operation processes artifact bundles atomically, ensuring that all resources in the bundle are published together or the entire operation fails. This maintains the integrity of artifact packages and their dependencies.

The operation validates that:

  1. The bundle conforms to CRMIPublishableBundle profile
  2. The first entry contains an ImplementationGuide
  3. All bundle entries have proper transaction requests
  4. Referenced resources within the bundle are consistent
 <status value="active"/> <kind value="operation"/> <date value="2026-05-11T04:30:28+00:00"/> <publisher value="HL7 International / Clinical Decision Support"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/dss"/> </telecom> </contact> <description value="The CRMI publish operation processes a publishable bundle containing artifacts and their metadata. This operation is based on the core FHIR Bundle operation but requires that the input Bundle conforms to the CRMIPublishableBundle profile. The bundle must be of type 'transaction' and must contain an ImplementationGuide resource as the first entry. The operation enables atomic publication of related artifacts (such as Libraries, ActivityDefinitions, PlanDefinitions, Measures, etc.) along with their governing ImplementationGuide, ensuring consistent deployment and proper metadata management."/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> </coding> </jurisdiction> <affectsState value="true"/> <code value="publish"/> <comment value="The CRMI publish operation processes artifact bundles atomically, ensuring that all resources in the bundle are published together or the entire operation fails. This maintains the integrity of artifact packages and their dependencies. The operation validates that: 1. The bundle conforms to CRMIPublishableBundle profile 2. The first entry contains an ImplementationGuide 3. All bundle entries have proper transaction requests 4. Referenced resources within the bundle are consistent "/> <system value="true"/> <type value="false"/> <instance value="false"/> <parameter> <name value="bundle"/> <use value="in"/> <min value="1"/> <max value="1"/> <documentation value="The publishable bundle to be processed. The bundle must conform to the CRMIPublishableBundle profile, meaning: - Bundle type must be 'transaction' - First entry must contain an ImplementationGuide resource - All entries must have proper transaction request information The bundle contains all related artifacts that should be published as an atomic unit."/> <type value="Bundle"/> <targetProfile value="http://hl7.org/fhir/uv/crmi/StructureDefinition/crmi-publishable-bundle"/> </parameter> <parameter> <name value="return"/> <use value="out"/> <min value="1"/> <max value="1"/> <documentation value="The bundle transaction response containing the results of processing each entry in the input bundle. Each entry in the response bundle corresponds to an entry in the input bundle and contains: - The HTTP status code for the transaction - The location of the created/updated resource (if successful) - Any operation outcomes or error messages The response follows the same structure as the core FHIR Bundle transaction response."/> <type value="Bundle"/> </parameter> </OperationDefinition>