Unattributed Code Systems

Copyright Fragment

This fragment is available on download.html

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web profiles.ihe.net Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
web profiles.ihe.net Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
web profiles.ihe.net
web profiles.ihe.net
web github.com Shared Managament of Radiation Treatments, published by IHE Radiation Oncology Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/RO.SMRT/ and changes regularly. See the Directory of published versions
web www.ihe.net IG © 2025+ IHE Radiation Oncology Technical Committee . Package ihe.ro.smrt#0.0.1-current based on FHIR 4.0.1 . Generated 2026-09-10
Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web github.com Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web github.com Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web profiles.ihe.net Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web www.ihe.net Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web profiles.ihe.net Requesters and Responders implementing this transaction SHALL provide a CapabilityStatement Resource as described in ITI TF-2: Appendix Z.3 indicating the transaction has been implemented.
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 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 dicom.nema.org See DICOM PS3.3 C.7.3 .
web dicom.nema.org See DICOM PS3.3 C.12.1 .
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 nema.org DICOM Tag Mapping
web www.rsna.org The performed procedure code
Binding: http://www.rsna.org/RadLex_Playbook.aspx ( extensible ) : The performed procedure type.
web www.rsna.org 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
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 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 dicom.nema.org http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1
web profiles.ihe.net IHE uses the normative words: Shall, Should, and May according to standards conventions .
web profiles.ihe.net The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z .
web profiles.ihe.net Editor, add the following new or modified actors to the IHE Technical Frameworks General Introduction Appendix A :
web profiles.ihe.net Editor, add the following new or modified transactions to the IHE Technical Frameworks General Introduction Appendix B :
web profiles.ihe.net Editor, add the following new or modified terms to the IHE Technical Frameworks General Introduction Appendix D :
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this profile. General definitions of actors are given in the Technical Frameworks General Introduction Appendix A . IHE Transactions can be found in the Technical Frameworks General Introduction Appendix B . Both appendices are located at https://profiles.ihe.net/GeneralIntro/ .
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this profile. General definitions of actors are given in the Technical Frameworks General Introduction Appendix A . IHE Transactions can be found in the Technical Frameworks General Introduction Appendix B . Both appendices are located at https://profiles.ihe.net/GeneralIntro/ .
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this profile. General definitions of actors are given in the Technical Frameworks General Introduction Appendix A . IHE Transactions can be found in the Technical Frameworks General Introduction Appendix B . Both appendices are located at https://profiles.ihe.net/GeneralIntro/ .
web profiles.ihe.net ITI TF-2: 3.30
web profiles.ihe.net ITI TF-2: 3.31
web profiles.ihe.net For more details see ITI-30
web profiles.ihe.net For more details see ITI-31
web www.ihe.net For more details see RAD TF-2 : 4.48.
web ihe.net The author should pay special consideration to security profiles in this grouping section. Consideration should be given to Consistent Time (CT) Client, ATNA Secure Node or Secure Application, as well as other profiles. For the sake of clarity and completeness, even if this table begins to become long, a line should be added for each actor for each of the required grouping for security. Also see the ITI document titled 'Cookbook: Preparing the IHE Profile Security Section' at http://ihe.net/Technical_Frameworks/#IT for a list of suggested IT and security groupings.
web en.wikipedia.org In the context of the $process-message operation, the Receiver is treated as a "black box" and simply accepts and processes the submitted data and there are no further expectations beyond the http level response as defined in the FHIR specification.
  • The Receiver may sort and filter notifications based on the MessageHeader.event codes. For example, notification-admit can be used to filter for TODO notifications.
web mermaid.js.org Modify the following "Swimlane Diagram". You can use plantuml or mermaid. see details on using mermaid in the IG publisher . Mermaid user guide online . Plantuml seems more stable, and does support clickable links on artifacts. Goto plantuml.com for an online tool to draft plantuml files.
web plantuml.com Modify the following "Swimlane Diagram". You can use plantuml or mermaid. see details on using mermaid in the IG publisher . Mermaid user guide online . Plantuml seems more stable, and does support clickable links on artifacts. Goto plantuml.com for an online tool to draft plantuml files.
web profiles.ihe.net See ITI TF-2x: Appendix Z.8 "Mobile Security Considerations"
web profiles.ihe.net IHE FHIR based profiles should reference the ITI Appendix Z section 8 Mobile Security and Privacy Considerations base when appropriate.
web wiki.ihe.net This section is informative, not normative. It is intended to put this profile in context with other profiles. Any required groupings should have already been described above. Brief descriptions can go directly into this section; lengthy descriptions should go into an appendix. Examples of this material include ITI Cross Community Access (XCA) Grouping Rules (Section 18.2.3), the Radiology associated profiles listed at wiki.ihe.net, or ITI Volume 1 Appendix E "Cross Profile Considerations", and the "See Also" sections Radiology Profile descriptions on the wiki such as http://wiki.ihe.net/index.php/Scheduled_Workflow#See_Also . If this section is left blank, add "Not applicable."

Internal Images

tree-filter.png
tree-filter.png