DocumentReference

Top  Previous  Next

A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The following types of documents can be searched for using the type search parameter:

11488-4 (Consultation Note)

18842-5 (Discharge Summary Note)

34117-2 (History & Physical)

28570-0 (Procedure Note)

11506-3 (Progress Note)

 

The following are also available via reference:

Imaging Narrative

Laboratory Report Narrative

Pathology Report Narrative

 

 

Response Description

Sample Response

{

  "resourceType": "DocumentReference",

  "id": "DEV-DEV-11913-D10692",

  "meta": {

     "lastUpdated": "2022-10-25T12:00:00-04:00",

     "profile": [

        "http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference"

     ]

  },

  "text": {

     "status": "generated",

     "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><table><tbody><tr><td>Patient:</td><td>Cole Andersonian, Sr. (DEV-DEV-11913)</td></tr><tr><td>Document#:</td><td>D10692</td></tr><tr><td>Accession#:</td><td>0014797</td></tr><tr><td>Author:</td><td>Steven Aspen, M. D. (117)</td></tr><tr><td>Clinical Date:</td><td>11/07/2022 17:33:00.000</td></tr><tr><td>Description:</td><td>Lower Extremities: consult</td></tr></tbody></table></div>"

  },

  "identifier": [

     {

        "system": "https://pai.healthcare",

        "value": "D10692"

     }

  ],

  "status": "current",

  "type": {

     "coding": [

        {

           "system": "http://loinc.org",

           "code": "11488-4",

           "display": "Consultation Note"

        }

     ],

     "text": "Consultation Note"

  },

  "date": "2022-10-25T12:00:00-04:00",

  "subject": {

     "reference": "Patient/DEV-DEV-11913",

     "display": "Cole Andersonian, Sr. (DEV-DEV-11913)"

  },

  "author": [

     {

        "reference": "Practitioner/117",

        "display": "Steven Aspen, M. D."

     }

  ],

  "category": [

     {

        "coding": [

           {

              "system": "http://hl7.org/fhir/us/core/CodeSystem/us-core-documentreference-category",

              "code": "clinical-note",

              "display": "Clinical Note"

           }

        ]

     }

  ],

  "custodian": {

     "reference": "Organization/DEV-DEV-PRACTICE"

  },

  "description": "Lower Extremities: consult",

  "context": {

     "encounter": [

        {

           "reference": "Encounter/DEV-DEV-11913-0014797",

           "display": "11/07/2022 at 9:30 am, MRI L/Knee with provider 117 at location OF1"

        }

     ],

     "period": {

        "start": "2022-11-07",

        "end": "2022-11-07"

     }

  },

  "content": [

     {

        "attachment": {

           "contentType": "application/msword",

           "data": {base64 encoded data}

        },

        "format": {

           "system": "urn:oid:1.3.6.1.4.1.19376.1.2.3",

           "code": "urn:ihe:iti:xds:2017:mimeTypeSufficient",

           "display": "mimeType Sufficient"

        }

     }

  ]

}

 

 

DocumentReference.id

 

The logical ID of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Cardinality

0..1

Type

string

Comment

The only time that a resource does not have an ID is when it is being submitted to the server using a create operation.

 

 

DocumentReference.meta

 

Metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

Cardinality

0..1

Type

Meta

 

 

DocumentReference.text

 

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative.

Cardinality

0..1

Type

Narrative

Comment

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

 

 

DocumentReference.identifier

 

Identifiers associated with the document, including version independent identifiers.

Cardinality

0..*

Type

Identifier

Comment

This is a business identifier, not a resource identifier

 

 

DocumentReference.status

 

The status of the diagnostic report.

Cardinality

1..1

Type

code: SHALL be taken from DocumentReferenceStatus

Requirements

This is the status of the DocumentReference object, which might be independent from the docStatus element.

 

 

DocumentReference.type

 

Specifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note).

Cardinality

1..1

Type

CodeableConcept US Core DocumentReference Type

Comment

Key metadata element describing the document that describes he exact type of document. Helps humans to assess whether the document is of interest when viewing a list of documents.

 

 

DocumentReference.date

 

When the document reference was created.

Cardinality

0..1

Type

instant

Comment

Referencing/indexing time is used for tracking, organizing versions and searching.

 

 

DocumentReference.subject

 

Who or what the document is about. The document can be about a patient or healthcare practitioner.

Cardinality

1..1

Type

Reference(USCorePatientProfile)

 

 

DocumentReference.author

 

Identifies who is responsible for adding the information to the document. If available, will be the provider responsible for this part of the patient's care.

Cardinality

0..1

Type

Reference(USCorePractitionerProfile)

Comment

Not necessarily who did the actual data entry (i.e. typist) or who was the source (informant).

 

 

DocumentReference.category:us-core

 

A categorization for the type of document referenced - helps for indexing and searching. Currently supports only clinical-note value.

Cardinality

0..*

Type

CodeableConcept US Core DocumentReference Category

Comment

Key metadata element describing the the category or classification of the document. This is a broader perspective that groups similar documents based on how they would be used. This is a primary key used in searching.

 

 

DocumentReference.description

 

A description of the source document.

Cardinality

0..1

Type

string

Requirements

Helps humans to assess whether the document is of interest.

 

 

DocumentReference.context

 

The clinical context in which the document was prepared.

Cardinality

0..1

Type

BackboneElement

Comment

These values are primarily added to help with searching for interesting/relevant documents.

 

 

DocumentReference.context.encounter

 

Describes the clinical encounter or type of care that the document content is associated with.

Cardinality

0..1

Type

Reference(USCoreEncounterProfile)

 

 

DocumentReference.context.period

 

Time of service that is being documented.

Cardinality

0..1

Type

Period

 

 

DocumentReference.content

 

The document and format referenced. There may be multiple content element repetitions, each with a different format.

Cardinality

1..*

Type

BackboneElement

 

 

DocumentReference.content.attachment

 

The document along with critical metadata to prove content has integrity.

Cardinality

1..1

Type

Attachment

 

 

DocumentReference.content.attachment.contentType

 

Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.

Cardinality

0..1

Type

code: MimeType

Requirements

Processors of the data need to be able to know how to interpret the data.

 

 

DocumentReference.content.attachment.data

 

Data inline, base64ed.

Cardinality

0..1

Type

base64Binary

Requirements

The data needs to able to be transmitted inline.

 

 

DocumentReference.content.attachment.url

 

Uri where the data can be found.

Cardinality

0..1

Type

url

Requirements

The data needs to be transmitted by reference.

 


 

Search

 

URL Syntax

Two HTTP methods are supported for searching: GET and POST. It is recommended to use HTTP POST.

Visit the FHIR Sandbox to try requests.

 

 

HTTP GET - searching

https://sandbox.pai.healthcare/preview/fhir/DocumentReference?{query string}

 

HTTP GET - return single record

https://sandbox.pai.healthcare/preview/fhir/DocumentReference/{resource id}

 

HTTP POST - searching

https://sandbox.pai.healthcare/preview/fhir/DocumentReference/_search

Set the Content-Type header to application/x-www-urlencoded

The body of the request is a similar query string used in the GET type of request detailed above.

 

 

Error Handling

If no records are returned or invalid search parameters are provided, then an HTTP 400 Bad Request is returned.

The body of the response will be an OperationOutcome.

 

 

Supported Search Parameters

 

_id

Corresponds to

DocumentReference.id

Search

exact

Example

https://sandbox.pai.healthcare/preview/fhir/DocumentReference/DEV-DEV-11913-d10691

 

Returns Document# 10691 of account 11913 in practice dev.

 

patient

Corresponds to

DocumentReference.subject

Search

exact

Required

true

Example

https://sandbox.pai.healthcare/preview/fhir/DocumentReference?patient=DEV-DEV-baddocs

 

Returns all Documents for patient baddocs in practice dev.

 

type

Corresponds to

DocumentReference.type

Search

exact

Acceptable Values

11488-4

18842-5

34117-2

28570-0

11506-3

Example

https://sandbox.pai.healthcare/preview/fhir/DocumentReference?patient=DEV-DEV-11913&type=11506-3

 

Returns Documents with LOINC code 11506-3 (progress notes) for patient 11913.

 

category

Corresponds to

DocumentReference.category

Search

exact

Example

https://sandbox.pai.healthcare/preview/fhir/DocumentReference?patient=DEV-DEV-11913&category=clinical-note

 

Returns the clinical notes Documents for patient 11913. As the only category provided in the value list is clinical-note, all documents will be returned.

 

date

Corresponds to

DocumentReference.date

Search

exact using the format of yyyy-MM-dd

Modifiers

ge - greater than or equal to

gt - greater than

le - less than or equal to

lt - less than

eq - equal to

Example

https://sandbox.pai.healthcare/preview/fhir/DocumentReference?patient=DEV-DEV-11913&category=clinical-note&date=ge2022-10-24

 

Returns the clinical notes Documents for patient 11913 for dates on or after 10/24/2022.