http://unstats.un.org/unsd/methods/m49/m49.htm
https://profiles.ihe.net/ITI/BALP/CodeSystem/BasicAuditEntityType
urn:ihe:event-type-code
This fragment is available on download.html
This publication includes IP covered under the following statements.
Type | Reference | Content |
---|---|---|
web | profiles.ihe.net | Recommend ATNA , encouraged IHE-IUA or SMART-on-FHIR |
web | profiles.ihe.net | Recommend ATNA , encouraged IHE-IUA or SMART-on-FHIR |
web | profiles.ihe.net |
![]() |
web | profiles.ihe.net |
![]() |
web | github.com | Sharing Valuesets, Codes, and Maps (SVCM), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.5.2-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.SVCM/ and changes regularly. See the Directory of published versions |
web | www.ihe.net |
IG © 2023+ IHE IT Infrastructure Technical Committee
. Package ihe.iti.svcm#1.5.2-current based on FHIR 4.0.1
. Generated 2025-04-28
Links: Table of Contents | QA Report | New Issue | Issues Version History | ![]() ![]() |
web | github.com |
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
![]() ![]() |
web | github.com |
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
![]() ![]() |
web | profiles.ihe.net |
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
![]() ![]() |
web | www.ihe.net |
Links: Table of Contents
|
QA Report
| New Issue
| Issues
Version History
|
![]() ![]() |
web | profiles.ihe.net | A Terminology Repository shall support responding to a request for both the JSON and the XML messaging formats as defined in FHIR. A Terminology Consumer shall accept either the JSON or the XML messaging formats as defined in FHIR. See ITI TF-2: Appendix Z.6 for more details. |
web | profiles.ihe.net | See ITI TF-2: Appendix Z.6 for informative implementation material for this transaction. |
web | profiles.ihe.net | See ITI TF-2: Appendix Z.6 for more details on response format handling. See ITI TF-2: Appendix Z.7 for handling guidance for Access Denied. |
web | profiles.ihe.net | See ITI TF-2: Appendix Z.6 for more details on response format handling. See ITI TF-2: Appendix Z.7 for handling guidance for Access Denied. |
web | profiles.ihe.net | See ITI TF-2: Appendix W for informative implementation material for this transaction. |
web | profiles.ihe.net | The requested format of the response from the mime-type value set. See ITI TF-2: Appendix Z.6 . |
web | profiles.ihe.net | The requested format of the response from the mime-type value set. See See ITI TF-2: Appendix Z.6 . |
web | github.com | The source code for this Implementation Guide can be found on IHE ITI.SVCM Github Repo . |
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 | github.com | IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted at ITI Public Comments . |
web | www.ihe.net | IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted at ITI Public Comments . |
web | github.com | As issues are submitted they will be managed on the SVCM GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later). |
web | wiki.ihe.net | As issues are submitted they will be managed on the SVCM GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later). |
web | www.ihe.net | As issues are submitted they will be managed on the SVCM GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later). |
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 | This section defines the actors, transactions, and/or content modules in this profile. Further information about actor and transaction definitions can be found in the IHE Technical Frameworks General Introduction Appendix A: Actors and Appendix B: Transactions . |
web | profiles.ihe.net | This section defines the actors, transactions, and/or content modules in this profile. Further information about actor and transaction definitions can be found in the IHE Technical Frameworks General Introduction Appendix A: Actors and Appendix B: Transactions . |
web | profiles.ihe.net | In addition to an IHE Integration Statement, the Terminology Consumer and Terminology Responder shall provide a CapabilityStatement Resource indicating the capabilities defined for all the transactions implemented including all query parameters implemented. See ITI TF-2: Appendix Z.4 . |
web | profiles.ihe.net | ITI TF-1: 9 |
web | profiles.ihe.net |
Some value sets, code systems, and concept maps have business identifiers, e.g., OIDs. See Section
ITI TF-2: Z.9.1
. In SVCM,
these business identifiers should be stored in the .identifier
element. The FHIR specification strongly
recommends using an http URL in the .url
element, but if this is not possible, then the .url
element
can contain a URI, for example, an OID as urn:oid:X.X.X.
|
web | profiles.ihe.net | See ITI TF-2: Appendix Z.8 “Mobile Security Considerations” . |
web | profiles.ihe.net | When an SVCM Terminology Repository is grouped with an SVS Value Set Repository, then it should ensure the business identifiers are aligned. SVS uses OIDs as value set ids. SVCM stores these in the ValueSet.identifier element. See Section 51.4.1.2 . |