|
Type
|
Reference
|
Content
|
|
web
|
www.ihe.net
|
contact
: https://www.ihe.net/ihe_domains/quality_research_and_public_health/
, qrph@ihe.net
, IHE QRPH Technical Committee: qrph@ihe.net
|
|
web
|
ihe.net
|
url
: http://ihe.net/qrph/madx/TBdiagnosisResult-stratifiers-example
|
|
web
|
ihe.net
|
http://ihe.net/qrph/madx/TBdiagnosisResult-stratifiers-example
|
|
web
|
profiles.ihe.net
|
|
|
web
|
profiles.ihe.net
|
|
|
web
|
github.com
|
Mobile Aggregate Data Exchange, published by IHE QRPH Technical Committee. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/QRPH.mADX/
and changes regularly. See the Directory of published versions
|
|
web
|
www.ihe.net
|
IG © 2021+ IHE QRPH Technical Committee
. Package ihe.qrph.madx#3.0.0 based on FHIR 4.0.1
. Generated 2025-08-21
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
|
See ITI TF-2: Appendix Z
|
|
web
|
github.com
|
The source code for this Implementation Guide can be found on IHE GitHub
|
|
web
|
profiles.ihe.net
|
IHE uses the normative words: “REQUIRED”, “REQUIRED NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” according to standards conventions
.
|
|
web
|
profiles.ihe.net
|
The use of RequiredSupport
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 can be submitted to the QRPH Public Comment form
.
|
|
web
|
www.ihe.net
|
IHE welcomes New Issues
from the GitHub community.
For those without GitHub access, issues can be submitted to the QRPH Public Comment form
.
|
|
web
|
github.com
|
As issues are submitted they will be managed on the QRPH GitHub Issues
, where discussion and workarounds can 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 QRPH GitHub Issues
, where discussion and workarounds can 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 QRPH GitHub Issues
, where discussion and workarounds can 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
|
github.com
|
mADX_014: According to the comment
received in the public-comment phase, the QM IG will receive enhancements that will benefit the mADX profile. These enhancements would bring a better solution for the way the stratification value sets are represented in mADX Measure (in mADX this is currently done via a cross-reference between the stratification component code and an instance of the relatedArtifact element). Once the QM IG is updated, we could add a dependency to it and utilize the enhancements.
|
|
web
|
www.ihe.net
|
mADX_001: How will mADX handle what is covered in Appendix 8D - Formatting of times and time intervals in mADX?
Resolution
: mADX does not include ADX to mADX mapping. This may be included in the IHE QRPH Clinical Quality Language for ADX White Paper
.
|
|
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
|
The Care Services Update Supplier is defined in the mCSD Profile in Section 1:46.1.1.4
.
|
|
web
|
profiles.ihe.net
|
The Care Services Update Consumer is defined in the mCSD Profile in Section 1:46.1.1.3
.
|
|
web
|
profiles.ihe.net
|
The Mobile Care Services Discovery (mCSD) Profile supports RESTful queries for organization units via the FHIR Location resource. Locations are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies. Locations also include political administrative area, such as a village district or region. A Location has a unique identifier and may have geographic attributes (address, geocode), contact attributes, and other attributes such as hours of operation. This location data is made available via the Request for Care Services Updates transaction initiated by a Care Services Update Consumer against a Care Services Update Supplier. See ITI TF-2: Appendix Z.8
for common mobile security considerations.
|
|
web
|
wiki.ihe.net
|
The QRPH registry of OIDs is located at https://wiki.ihe.net/index.php/QRPH_Registry
|
