This is a search for Pages, Articles, and Resources. Switch to a scoped search for Resources to find Products, Components, and Guides.
My Health Record FHIR Gateway - Security Requirements and Guidelines v1.2
Component
DH-3706:2023
Status
Active
Version
1.2
This document specifies the mandatory security requirements and recommended security guidelines for applications (apps) connecting with the My Health Record system APIs via the FHIR® standard gateway, using interaction models #1 or #4 (refer to Appendix A for details).
… (refer to Appendix A for details). … DH-3706-2023-My Health Record FHIR Gateway - …
My Health Record Mobile Developer Welcome Pack v1.7
The My Health Record Mobile Developer Welcome Pack is a collection of forms and guides to help new app developers connect to the My Health Record system for the first time. This version includes updated versions of each document to note the inclusion of share functionality and the Get XML View functionality. A preview copy of the Portal Operator…
My Health Record - Portal Operator – Production Environment Access Request (PEAR) Form v3.7
Component
DH-3703:2023
Status
Active
Version
3.7
The purpose of this form is for mobile app developers to request access to the My Health Record Production Environment by providing information about the developer’s organisation, details of their application (app), declaring that the app conforms to the mandatory My Health Record requirements and technical specifications and has undergone the…
… and has undergone the… … DH-3703-2023 - My Health Record - Portal …
My Health Record FHIR Gateway - Presentation Requirements and Guidelines v1.2
Component
DH-3707:2023
Status
Active
Version
1.2
This document is designed to provide developers of applications (apps) accessing the My Health Record system through its FHIR Gateway with guidelines and requirements for the on-screen presentation of structured, non-CDA My Health Record data.
… non-CDA My Health Record data. … DH-3707-2023-My Health Record FHIR Gateway - …
My Health Record FHIR Gateway - CCD Risk Based Approach – Risk Assessment Questionnaire v1.1
Component
DH-3709:2023
Status
Active
Version
1.1
As a part of the vendor onboarding process, the proposed app or new functionality must undergo a risk assessment. The risk assessment is performed by reviewing user stories, requirements and consent workflows.
… requirements and consent workflows. … DH-3709-2023-My Health Record - FHIR Mobile …
My Health Record - Portal Operator Registration Agreement (Preview Copy) v24022023
Component
DH-3708:2023
Status
Active
Version
24022023
Note: Preview Copy only. The purpose of this Agreement is to satisfy the System Operator that the person applying to be a Registered Portal Operator:-complies with the My Health Records Act and Rules, and-agrees to be bound by the conditions of registration outlined in this document. By entering into this Agreement you are applying for the System…
My Health Record FHIR Gateway - Operations Requirements and Guidelines v1.2
Component
DH-3704:2023
Status
Active
Version
1.2
The purpose of this document is to define the operations requirements and guidelines for applications (apps) connecting with the My Health Record system APIs via the My Health Record FHIR® Gateway, using interaction models #1 or #4 (refer to Appendix A for details).
… (refer to Appendix A for details). … DH-3704-2023-My Health Record FHIR Gateway - …
My Health Record FHIR Gateway - Consent Requirements and Guidelines v1.2
Component
DH-3705:2023
Status
Active
Version
1.2
The purpose of this document is to define the consent requirements and guidelines for applications (apps) connecting with the My Health Record system APIs via the FHIR® standard gateway, using interaction models #1 or #4 (refer to Appendix A for details).
… (refer to Appendix A for details). … DH-3705-2023-My Health Record FHIR Gateway - …
Australian Digital Health Agency (ADHA) OID Repository
Guide
DG-3127
OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.
… is taken fromNote: The OID is a leaf node - it is used in a coded data element … length. Note: The OID is a leaf node - it is used in a coded data element …
PCA™ - Count and paging
The _count search parameter returns the number of requested resources per page (excluding the resources returned with _include search parameter) as requested by the client.
PCA™ - Create practitioner role
Now that you have created an Organization and HealthcareService at a Location, and have found a Practitioner, you can create a PractitionerRole.
My Health Record B2B Gateway - Upload document
This guide will walk through the steps to create and upload clinical documents
… = BaseCDAModel.CreateCodableText("28237011000036107", CodingSystem.AMTV3, …