Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-45634

Technical considerations for the Hub storing current content

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIRCast (FHIR)
    • 3.0.0-ballot
    • Infrastructure & Messaging
    • STU
    • Content Sharing
    • Hide

      Same resolution as: https://jira.hl7.org/browse/FHIR-45632

      We will clarify in the spec that 

      For FHIRcast –  we don't propose limits on the number of entries in the transaction, although implementers should expect a limit for production-grade software. Generally, the upper range of entries in a FHIRcast transaction bundle is in the *dozens.*

      Recipients of FHIRcast event noticiations that are larger than they can support SHOULD return an error – {}via either an HTTP error status with a spec defined error code, or a syncerror with a spec-defined OperationOutcome code. 

      Show
      Same resolution as: https://jira.hl7.org/browse/FHIR-45632 We will clarify in the spec that  For FHIRcast –  we don't propose limits on the number of entries in the transaction, although implementers should expect a limit for production-grade software. Generally, the upper range of entries in a FHIRcast transaction bundle is in the  *dozens .* Recipients of FHIRcast event noticiations that are larger than they can support SHOULD return an error –  { }via either an HTTP error status with a spec defined error code, or a syncerror with a spec-defined OperationOutcome code.  HTTP 413 - Content Too Large    OperationOutcome.issue.code = " too-long "
    • Enhancement
    • Non-compatible

      One of the responsibilities of the Hub is to maintain a list of current FHIR resource content in the anchor context.  This has the possibility to grow indefinitely so the spec should provide a recommended error or call out the possibility that the Hub may need to flush or remove content from the context for technical reasons in the event that a long running content sharing session accrues an unmanageable number of resources.

            Unassigned Unassigned
            azliu Alexander Liu
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: