This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example Subscription/example (XML)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No defined compartments

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

Example of subscription (id = "example")

<?xml version="1.0" encoding="UTF-8"?>

<Subscription xmlns="http://hl7.org/fhir">
  <id value="example"/> 
  <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: Subscription</b> <a name="example"> </a> <a name="hcexample"> </a> </p> <div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border:
       1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Resource Subscription &quot;example&quot; </p> </div> <p> <b> identifier</b> : <a href="http://terminology.hl7.org/5.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes
         defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase)
         and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.t

This oid is used as an identifier II.root to indicate the the extension is an absolute
         URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that
         when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid
         or urn:uuid: 

Note that this OID is created to aid with interconversion between CDA and FHIR
         - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear
         more commonly in FHIR.

This OID may also be used in CD.codeSystem.">URI</a> /urn:uuid:97e5aa1e-5916-4512-a36e-24eef784e3cc</p> <p> <b> name</b> : Example</p> <p> <b> status</b> : active</p> <p> <b> topic</b> : <a href="http://example.org/R5/SubscriptionTopic/example">http://example.org/R5/SubscriptionTopic/example</a> </p> <p> <b> contact</b> : ph: (555) 555-1212(WORK)</p> <p> <b> reason</b> : Example subscription for example topic</p> <h3> FilterBies</h3> <table class="grid"><tr> <td style="display: none">-</td> <td> <b> Resource</b> </td> <td> <b> FilterParameter</b> </td> <td> <b> Value</b> </td> </tr> <tr> <td style="display: none">*</td> <td> <a href="encounter.html">Encounter</a> </td> <td> patient</td> <td> Patient/123</td> </tr> </table> <p> <b> channelType</b> : rest-hook (Details: [not stated] code rest-hook = 'rest-hook', stated as 'null')</p> </div> </text> <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:uuid:97e5aa1e-5916-4512-a36e-24eef784e3cc"/> 
  <name value="Example"/> 
  <status value="active"/> 
  <topic value="http://example.org/R5/SubscriptionTopic/example"/> 
    <system value="phone"/> 
    <value value="(555) 555-1212"/> 
    <use value="work"/> 
  <reason value="Example subscription for example topic"/> 
    <resource value="http://hl7.org/fhir/StructureDefinition/Encounter"/> 
    <filterParameter value="patient"/> 
    <value value="Patient/123"/> 
    <code value="rest-hook"/> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.