Difference between revisions of "Deliver Message"

From Hiasobi - FHIR
Jump to: navigation, search
(Message Bundle)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
Profile for delivery of PDF documents via FHIR interface
 
Profile for delivery of PDF documents via FHIR interface
* send a Bundle of resources to the base url of the Hiasobi FHIR server
+
 
 +
=Message Bundle=
 +
* send a Bundle of resources to the base url of the Hiasobi FHIR server e.g. https://localhost:8102
 +
* this is a transaction
 +
 
 +
* Bundle
 +
** MessageHeader
 +
** Patient
 +
** Practitioner
 +
** Organization
 +
** DocumentReference
 +
 
 +
=Communication Bundle=
 +
* send a Bundle of resources to the base url of the Hiasobi FHIR server e.g. https://localhost:8102
 
* Bundle.entry -'fullUrl' value use "urn:uuid:" to allow resources to reference others within the bundle
 
* Bundle.entry -'fullUrl' value use "urn:uuid:" to allow resources to reference others within the bundle
* Currently restricted to this logical tree:
+
* this is a transaction
  
  
Line 8: Line 21:
 
** Communication - record of document submission
 
** Communication - record of document submission
 
*** (sent): date-time of submission
 
*** (sent): date-time of submission
*** (Communication.recipient) Organization - receiving organisation
+
*** (Communication.recipient) Organization - value receiving organisation  
 
**** (name) - recipient name
 
**** (name) - recipient name
*** (Communication.sender) Practitioner - sender of the document
+
*** (Communication.sender) Practitioner - reference to sender of the document
**** (name) - sending practitioner name
+
*** (Communication.subject)Patient - reference to subject of the document
**** (identifier) - Provider Number (optional)
+
**** (practitionerRole.managingOrganization) Organization - associated practice details for practitioner (can be same as patient)
+
*** (Communication.subject)Patient - subject of the document
+
**** (name) - patient name
+
**** (identifier) - Medicare Number, DVA Number and/or IHI  (optional)
+
**** (birthDate) - date of birth
+
**** (gender) - coded gender of patient
+
**** (address) - details of address (optional)
+
**** (managingOrganization) Organization - associated practice details for patient (can be same as sender practitioner)
+
***** (name) - associated practice/clinic name
+
 
*** (Communication.payload.contentAttachment.url) Binary  - document content
 
*** (Communication.payload.contentAttachment.url) Binary  - document content
 
**** (content) - binary content base64
 
**** (content) - binary content base64
 
**** (contentType) - mime type, allowed application/pdf, application/rtf, text/html
 
**** (contentType) - mime type, allowed application/pdf, application/rtf, text/html
 +
 +
 +
Note: can include full resource entry for recipient, sender, subject (include in the bundle and use "urn:uuid:" reference) or relative resource reference to FHIR server location.
 +
 +
[[Example JSON Post PDF]]

Latest revision as of 17:00, 3 September 2018

Profile for delivery of PDF documents via FHIR interface

Message Bundle

  • send a Bundle of resources to the base url of the Hiasobi FHIR server e.g. https://localhost:8102
  • this is a transaction
  • Bundle
    • MessageHeader
    • Patient
    • Practitioner
    • Organization
    • DocumentReference

Communication Bundle

  • send a Bundle of resources to the base url of the Hiasobi FHIR server e.g. https://localhost:8102
  • Bundle.entry -'fullUrl' value use "urn:uuid:" to allow resources to reference others within the bundle
  • this is a transaction


  • Bundle
    • Communication - record of document submission
      • (sent): date-time of submission
      • (Communication.recipient) Organization - value receiving organisation
        • (name) - recipient name
      • (Communication.sender) Practitioner - reference to sender of the document
      • (Communication.subject)Patient - reference to subject of the document
      • (Communication.payload.contentAttachment.url) Binary - document content
        • (content) - binary content base64
        • (contentType) - mime type, allowed application/pdf, application/rtf, text/html


Note: can include full resource entry for recipient, sender, subject (include in the bundle and use "urn:uuid:" reference) or relative resource reference to FHIR server location.

Example JSON Post PDF