Difference between revisions of "Deliver to Inbox"

Latest revision as of 22:54, 3 May 2020

Deliver document(s) to inbox - matching on names, identifier, date of birth

Example JSON Delivery Submission

POST /

Bundle
  type - [ transaction | message ]
  1..1   MessageHeader
            id
            timestamp
            eventcoding - see fixed value
            source - name of sender
            destination 
              receiver
                reference - Practitioner/[practitioner id]
  1..1   Practitioner
            id
           identifier
             system
             value
          name
             family
             given
  1..1  Patient
           id
          name
              family
              given
         gender
         birthDate
  1..*  DocumentReference
            id
            type.text - entry type
            indexed
            status = current 
            content
              attachment
                contentType - [ application/pdf | application/rtf | text/plain ] mime type
                data - base64 content

Communication (outbound)

 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