Unattributed Code Systems

• http://unstats.un.org/unsd/methods/m49/m49.htm

Copyright Fragment

This fragment is available on download.html

Copyright and Registered Trademark Uses

• IG © 2025+ IHE Radiation Oncology Technical Committee. Package ihe.ro.smrt#0.0.1-current based on FHIR 4.0.1. Generated 2025-07-17 Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal ( src )
• hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
• 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 ( src )
• This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. Show Usage * LOINC: IheToDoLaughing, Observation/ex-IHE-ToDo-laugh-0 and ToDoLaugh ( src )
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html Show Usage * Observation Category Codes: Observation/ex-IHE-ToDo-laugh-0 and ToDoLaugh * ActCode: Encounter/ex-encounter * ActReason: Encounter/ex-encounter, Observation/ex-IHE-ToDo-laugh-0, Patient/ex-patient, Practitioner/ex-author and Practitioner/ex-practitioner * Confidentiality: Encounter/ex-encounter, Practitioner/ex-author and Practitioner/ex-practitioner ( src )

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 2025-07-17 Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	github.com	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	github.com	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	profiles.ihe.net	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	www.ihe.net	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	profiles.ihe.net	Note 2: See ITI TF-2: Appendix Z.2 for additional constraints on the use of the token search parameter type.
web	profiles.ihe.net	See ITI TF-2: Appendix Z.6 for details.
web	profiles.ihe.net	Based on the query results, the Responder SHALL either return an error or success. Guidance on handling Access Denied related to use of 200, 403 and 404 can be found in ITI TF-2: Appendix Z.7 .
web	profiles.ihe.net	The response SHALL adhere to any FHIR Bundle constraints specified in ITI TF-2: Appendix Z.1 .
web	profiles.ihe.net	Resource Bundling SHALL comply with the guidelines in ITI TF-2: Appendix Z.1 .
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	ucum.org	The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse Show Usage Unified Code for Units of Measure (UCUM) : Observation/ex-IHE-ToDo-laugh-0
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	**TODO: Explicitly state whether this is a Workflow, Transport, or Content Module (or combination) profile. See the IHE Technical Frameworks General Introduction for definitions of these profile types. The IHE Technical Frameworks General Introduction . **
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	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	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

anImage.png

tree-filter.png