- The FHIR Patient Reported Outcomes (PRO) Implementation Guide is included with the balloted, standard for trial use (STU) implementation guide and a link to the continuous build of the same. The latter, as a continuous integration build, may at any point in time be unavailable or undergoing change.
- The creation/generation and scoring of PRO measure instruments and interpretation of the PRO data is dictated by the organizations/institutions that created, tested, and validated them.
- The HL7 FHIR PRO IG is not intended to be used to define or generate PRO measure instruments or interpret PRO data.
- The FHIR PRO IG leverages the Structured Data Capture Implementation Specification and the profiles listed below to capture and exchange patient-reported outcome data:
- See the PRO project in the:
- The IHE-MHD profile can include data in the form of CDA, FHIR-Documents, or FHIR Bundles.
|
- PROM Instrument and Meta Data Security Conformance:
- SHALL support the Communication security mechanisms outlined in FHIR Security Specification.
- SHALL support the Authentication security mechanisms outlined in FHIR Security Specification.
- SHOULD support other security recommendations outlined in FHIR Security as appropriate.
- EHR or Care Delivery IT System Security Conformance:
- SHALL support the Communication security mechanisms outlined in FHIR Security Specification.
- SHALL support the Authentication security mechanisms outlined in FHIR Security Specification.
- SHOULD support other security recommendations outlined in FHIR Security as appropriate.
- External Pro Administration System Security Conformance:
- SHALL support the Communication security mechanisms outlined in FHIR Security Specification.
- SHALL support the Authentication security mechanisms outlined in FHIR Security Specification.
- SHOULD support other security recommendations outlined in FHIR Security as appropriate.
- Patient Facing Administration App System Security Conformance:
- SHALL support the Communication security mechanisms outlined in FHIR Security Specification.
- SHALL support the Authentication security mechanisms outlined in FHIR Security Specification.
- SHOULD support other security recommendations outlined in FHIR Security as appropriate.
- MAY have to comply with other security requirements to interact with the External Assessment Center.
- External Assessment Center Security Conformance:
- SHALL support the Communication security mechanisms outlined in FHIR Security Specification.
- SHALL support the Authenitication security mechanisms outlined in FHIR Security Specification.
- SHOULD support other security recommendations outlined in FHIR Security as appropriate.
- MAY have to comply with other security requirements to interact with the External Assessment Center.
- Feedback requested, as security is at the discretion of the implementing organization based on the ecosystem and operational considerations within each organization.
|
Submitted by John Moehrke on
IHE - Mobile Access to Health Documents
The IHE MHD implementation guide could be used to provide a method for patients to submit data with attribution. The data could be in the form of CDA, FHIR-Documents, or simply FHIR Bundles.