This page is part of the FHIR Specification (v0.0.82: (v1.0.2: DSTU 1). 2). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions

• Content
• Examples
• Formal Definitions Detailed Descriptions
• Mappings
• Profiles

6.12.6 6.16.6 Resource Conformance - Examples

Example Index: List:

6.12.6.1 </Conformance>

General Condition Example	XML	JSON
PHR Example	XML	JSON
Complete Conformance Statement	XML	JSON
EmptyConformanceStatement	XML	JSON
Terminology Server Base Conformance Statement General	XML General Condition Example (id = "example") Raw	JSON
USLabOrder Orderer	XML The EHR Server supports the following transactions for the resource Person: read, vread, update, history, search(name,gender), create and updates. http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/b5fdd9fc-b021-4ea1-911a -721a60663796 <!-- the identifier for this conformance statement. The identifier and version establish identifiers that other specifications etc may use to refer to the conformance statement that this resource represents in a logical manner rather than in a literal (URL) fashion The identifier should be globally unique - a UUID, an OID, or a URL/URI --> This is the FHIR conformance statement for the main EHR at ACME for the private interface - it does not describe the public interface <!-- while the FHIR infrastructure is turning over prior to development, a version is required. Note that this may be rescinded later? --> <!-- this system can do either xml or json. (Listing both implies full support for either, with interconversion) --> <!-- in a real conformance statement, it's unlikely that a single conformance statement would declare conformance for REST, messaging and documents, though it is legal. This example does so in order to show all the parts of a conformance statement --> <!-- this is a server conformance statement. Note that servers are required to provide one of these. It can easily be edited by hand - copy this, replace the metadata above, delete the messaging and document stuff below, and then replace the details appropriately. --> <!-- let's assume that HL7 has stood up a profile registry at http://fhir.hl7.org/fhir - it's likely to have a registry, though this is not decided, nor is a URL decided. This application simply uses a profile registered directly with HL7. For the simplest case of a FHIR REST Server, just delete this profile reference. Profile references do not need to be a UUID, though a profile registry could insist that they are --> <!-- a messaging conformance statement. Applications are not required to make a conformance statement with regard to messaging, though there is active argument that they should. --> <!-- specify a profile for the request person. Very often there's no point profiling the response, it's not interesting --> <!-- this is the important element: a reference to a published document profile note that this is a version specific reference. --> http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/b5fdd9fc-b021-4ea1-911a -721a60663796	JSON	from US Lab Implementation Guides IG
USLabOrder Receiver	XML	JSON	from US Lab Implementation Guides IG
USLabReport Sender	XML	JSON	from US Lab Implementation Guides IG
USLabReport Receiver	XML	JSON	from US Lab Implementation Guides IG
SDC Form authoring system	XML	JSON	from Structured Data Capture IG
SDC System for completing forms	XML	JSON	from Structured Data Capture IG
SDC Repository for forms	XML	JSON	from Structured Data Capture IG
SDC Repository for completed forms	XML	JSON	from Structured Data Capture IG
SDC System for archiving and retrieving the completed forms	XML	JSON	from Structured Data Capture IG
SDC Repository for Data Elements	XML	JSON	from Structured Data Capture - Data Element Exchange IG
SDC Data Elements author/maintenance system	XML	JSON	from Structured Data Capture - Data Element Exchange IG
	XML	JSON	from Data Access Framework IG
	XML	JSON	from Data Access Framework IG
System which records information about EHR events	XML	JSON	from EHRS Functional model - Record Lifecycle Events IG

General Condition Example 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.

{ "resourceType": "Conformance", "text": { "status": "generated", "div": "<div>\n <p>The EHR Server supports the following transactions for the resource Person: read, vread, \n update, history, search(name,gender), create and updates.</p>\n <p>The EHR System supports the following message: admin-notify::Person.</p>\n <p>The EHR Application has a <a href=\"http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile</a>.</p>\n </div>" }, "identifier": "68D043B5-9ECF-4559-A57A-396E0D452311", "version": "20130510", "name": "ACME EHR Conformance statement", "publisher": "ACME Corporation", "telecom": [ { "system": "email", "value": "wile@acme.org" } ], "description": "This is the FHIR conformance statement for the main EHR at ACME for the private interface - it does not describe the public interface", "date": "2012-01-04", "software": { "name": "EHR", "version": "0.00.020.2134" }, "fhirVersion": "0.07", "acceptUnknown": true, "format": [ "xml", "json" ], "rest": [ { "mode": "server", "resource": [ { "type": "Patient", "profile": { "reference": "http://fhir.hl7.org/base/Profile7896271d-57f6-4231-89dc-dcc91eab2416" }, "operation": [ { "code": "read" }, { "code": "vread" }, { "code": "update" }, { "code": "history-instance" }, { "code": "create" }, { "code": "history-type" } ] } ], "operation": [ { "code": "transaction" }, { "code": "history-system" } ] } ], "messaging": [ { "event": [ { "code": { "system": "http://hl7.org/fhir/message-type", "code": "admin-notify" }, "mode": "receiver", "focus": "Patient", "request": { "reference": "Profile/101" }, "response": { "reference": "Profile/101" } } ] } ], "document": [ { "mode": "consumer", "documentation": "Basic rules for all documents in the EHR system", "profile": { "reference": "http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/history/b5fdd9fc-b021-4ea1-911a-721a60663796" } } ] }