http://example.com/events/syncerror/your-error-code-system
http://unstats.un.org/unsd/methods/m49/m49.htm
This fragment is available on 6_change-log.html
This publication includes IP covered under the following statements.
| Type | Reference | Content |
|---|---|---|
| web | github.com | FHIRcast, published by HL7 International / Infrastructure And Messaging. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhircast-docs/ and changes regularly. See the Directory of published versions |
| web | developer.mozilla.org |
FHIRcast doesn't prescribe a limit on the number of entries in the transaction Bundle; however, 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 SHOULD return an error when they receive a FHIRcast event notification that is too large to support. Specifically, recipients SHALL either synchronously return an HTTP error status of HTTP 413 - Content Too Large
, or asynchronously a syncerror
with an OperationOutcome.issue.code
= " too-long
".
|
| web | www.iso.org | Expressed in Extended Backus-Naur Form (EBNF) notation, the FHIRcast syntax for OAuth 2.0 access scopes is: |
| web | github.com | New events are proposed in a prescribed format using the event template by submitting a pull request . FHIRcast events are versioned, and mature according to the event maturity model . |
| web | en.wikipedia.org | Event names are unique and case-insensitive. It is RECOMMENDED to use Upper-Camel case. |
| web | www.rfc-editor.org | A Subscriber's WebSocket connection is closed with any Connection Close Reason other than 1000 (normal closure) or 1001 (going away) (see WebSocket RFC and WebSocket Status Codes ) |
| web | www.rfc-editor.org | A Subscriber's WebSocket connection is closed with any Connection Close Reason other than 1000 (normal closure) or 1001 (going away) (see WebSocket RFC and WebSocket Status Codes ) |
| web | www.rfc-editor.org |
The Hub SHALL NOT generate
SyncError
events when a Subscriber closes its WebSocket connection to the Hub with a Connection Close Reason
of 1000 (normal closure) or 1001 (going away).
|
| web | devcenter.heroku.com | Heroku's excellent explanation of WebSocket security |
| web | en.wikipedia.org |
Imaging adds Observation A to the content sharing session (using a DiagnosticReport-update Event
) without storing this information in a persistent FHIR server. Imaging is responsible to generate a globally unique (e.g., a UUID
) Resource.id
and providing this as the Resource.id
in Observation A's entry in the FHIRcast update bundle
with the entry's request.method
attribute having a value of PUT
. Both the FHIRcast Hub and Reporting add this Observation to their working memory including the Resource.id
value provided by Imaging.
|
| web | github.com | All changes to the FHIRcast specification are tracked in the specification's HL7 github repository . Further, issues may be submitted and are tracked in jira or (historically as) github issues . For the reader's convenience, the below table additionally lists significant changes to the specification. |
| web | github.com | All changes to the FHIRcast specification are tracked in the specification's HL7 github repository . Further, issues may be submitted and are tracked in jira or (historically as) github issues . For the reader's convenience, the below table additionally lists significant changes to the specification. |
| web | www.rsna.org |
Copyright 2014 – The Radiological Society of North America (RSNA), all rights reserved. Licensed under RadLex License Version 2.0. You may obtain a copy of the license at: http://www.rsna.org/radlexdownloads/
This work is distributed under the above noted license on an “AS IS” basis, WITHOUT WARRANTIES OF ANY KIND, either express or implied. Please see the license for complete terms and conditions.Subject to the terms and conditions of this Agreement, Licensor hereby grants to You a worldwide, non-exclusive, no-charge, royalty-free copyright license to reproduce, prepare Adaptations of, publicly display, publicly perform, sublicense, and distribute the Work and such Adaptations in any medium.RadLex is licensed freely for commercial and non-commercial users. Review and download the license: http://www.rsna.org/uploadedFiles/RSNA/Content/Informatics/RadLex_License_Agreement_and_Terms_of_Use_V2_Final.pdf
Show Usage
|
| web | www.rsna.org |
Copyright 2014 – The Radiological Society of North America (RSNA), all rights reserved. Licensed under RadLex License Version 2.0. You may obtain a copy of the license at: http://www.rsna.org/radlexdownloads/
This work is distributed under the above noted license on an “AS IS” basis, WITHOUT WARRANTIES OF ANY KIND, either express or implied. Please see the license for complete terms and conditions.Subject to the terms and conditions of this Agreement, Licensor hereby grants to You a worldwide, non-exclusive, no-charge, royalty-free copyright license to reproduce, prepare Adaptations of, publicly display, publicly perform, sublicense, and distribute the Work and such Adaptations in any medium.RadLex is licensed freely for commercial and non-commercial users. Review and download the license: http://www.rsna.org/uploadedFiles/RSNA/Content/Informatics/RadLex_License_Agreement_and_Terms_of_Use_V2_Final.pdf
Show Usage
|
| web | en.wikipedia.org | Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ). |
| web | en.wikipedia.org |
A logical id of the resource SHALL be provided. It may be the id
associated with the resource as persisted in a FHIR server. If the resource is not stored in a FHIR server, the Subscriber requesting the context change SHOULD use a mechanism to generate the id
such that it will be globally unique (e.g., a UUID
). When a [FHIR resource]-close event including this report is requested, the Subscriber requesting the context be closed SHALL use the same DiagnosticReport id
which was provided in the [FHIR resource]-open event (see also FHIRcast DiagnosticReport for Close Events
).
|
| web | en.wikipedia.org |
A logical id of the resource SHALL be provided. It may be the id
associated with the resource as persisted in a FHIR server. If the resource is not stored in a FHIR server, the Subscriber requesting the context change SHOULD use a mechanism to generate the id
such that it will be globally unique (e.g., a UUID
). When a [FHIR resource]-close event including this encounter is requested, the Subscriber requesting the context be closed SHALL use the same Encounter id
which was provided in the [FHIR resource]-open event (see also FHIRcast Encounter for Close Events
).
|
| web | dicom.nema.org | If one or more series elements are present in the ImagingStudy, then there shall be one DICOM Study UID identifier (see DICOM PS 3.3 C.7.2 . |
| web | www.rsna.org |
Unless not suitable, these codes SHALL be taken from http://www.rsna.org/RadLex_Playbook.aspx
( extensible to http://www.rsna.org/RadLex_Playbook.aspx
)
|
| web | dicom.nema.org | See DICOM PS3.3 C.7.3 . |
| web | dicom.nema.org | See DICOM PS3.3 C.12.1 . |
| web | dicom.nema.org |
Unless not suitable, these codes SHALL be taken from http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1
( extensible to http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1
)
|
| web | www.rsna.org |
The performed procedure code Binding: http://www.rsna.org/RadLex_Playbook.aspx ( extensible ): The performed procedure type. |
| web | dicom.nema.org |
DICOM class type Binding: http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1 ( extensible ): The sopClass for the instance. |
| web | www.rsna.org |
http://www.rsna.org/RadLex_Playbook.aspx
http://www.rsna.org/RadLex_Playbook.aspx
|
| web | dicom.nema.org |
http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1
http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1
|
| web | en.wikipedia.org |
A logical id of the resource SHALL be provided. It may be the id
associated with the resource as persisted in a FHIR server. If the resource is not stored in a FHIR server, the Subscriber requesting the context change SHOULD use a mechanism to generate the id
such that it will be globally unique (e.g., a UUID
). When a [FHIR resource]-close event including this image study is requested, the Subscriber requesting the context be closed SHALL use the same ImagingStudy resource id
which was provided in the [FHIR resource]-open event (see also FHIRcast ImagingStudy for Close Events
).
|
| web | en.wikipedia.org |
A logical id of the resource SHALL be provided. It may be the id
associated with the resource as persisted in a FHIR server. If the resource is not stored in a FHIR server, the Subscriber requesting the context change SHOULD use a mechanism to generate the id
such that it will be globally unique (e.g., a UUID
). When a [FHIR resource]-close event including this patient is requested, the Subscriber requesting the context be closed SHALL use the same Patient id
which was provided in the [FHIR resource]-open event (see also FHIRcast Patient for Close Events
). Additionally, this id
SHALL be the id
used in the subject
attribute's Patient reference in all resources containing a subject
attribute in a given [FHIR resource]-open event.
|
| web | github.com | Check out our awesome community contributions on github |
| web | github.com | Log issues , submit a PR! |
| web | github.com | This Implementation Guide was made possible by the contributions of the HL7 Infrastructure & Messaging Workgroup and those identified below. |
|
ContentSharingEventName.png
|
|
ContextEventName.png
|
|
EventName.png
|
|
FhircastScopes.png
|
|
MultiplePatientOpens.png
|
|
PatientOpenAndClose.png
|
|
SelectionEventName.png
|
|
TransactionalUpdates.png
|
|
colorful overview diagram.png
|
|
information-svgrepo-com.svg
|
|
question-mark-in-a-circle-svgrepo-com.svg
|