Difference between revisions of "Deliver Message"
From Hiasobi - FHIR
Brett Esler (Talk | contribs) |
|||
Line 25: | Line 25: | ||
**** (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 | ||
+ | |||
+ | [Example JSON Post PDF] |
Revision as of 16:07, 18 April 2016
Profile for delivery of PDF documents via FHIR interface
- send a Bundle of resources to the base url of the Hiasobi FHIR server
- Bundle.entry -'fullUrl' value use "urn:uuid:" to allow resources to reference others within the bundle
- Currently restricted to this logical tree:
- Bundle
- Communication - record of document submission
- (sent): date-time of submission
- (Communication.recipient) Organization - receiving organisation
- (name) - recipient name
- (Communication.sender) Practitioner - sender of the document
- (name) - sending practitioner name
- (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
- (content) - binary content base64
- (contentType) - mime type, allowed application/pdf, application/rtf, text/html
- Communication - record of document submission
[Example JSON Post PDF]