2nd DSTU Draft For Comment
This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
Profile for conformance
{
"resourceType": "Profile",
"id": "Conformance",
"meta": {
"lastUpdated": "2015-02-23T09:07:27.665+11:00"
},
"text": {
"status": "generated",
"div": "<div>!-- Snipped for Brevity --></div>"
},
"url": "http://hl7.org/fhir/Profile/Conformance",
"name": "Conformance",
"publisher": "HL7 FHIR Project (FHIR Management Group)",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://hl7.org/fhir"
}
]
},
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fhirmg/index.cfm"
}
]
}
],
"description": "Base Profile for Conformance Resource",
"status": "draft",
"date": "2015-02-23T09:07:27+11:00",
"mapping": [
{
"identity": "rim",
"uri": "http://hl7.org/v3",
"name": "RIM"
}
],
"type": "Conformance",
"snapshot": {
"element": [
{
"path": "Conformance",
"short": "A conformance statement",
"definition": "A conformance statement is a set of requirements for a desired implementation or a description of how a target application fulfills those requirements in a particular implementation.",
"min": 1,
"max": "1",
"constraint": [
{
"key": "cnf-1",
"name": "Content Required",
"severity": "error",
"human": "A Conformance statement SHALL have at least one of rest, messaging or document",
"xpath": "exists(f:rest) or exists(f:messaging) or exists(f:document)"
},
{
"key": "cnf-2",
"name": "Details",
"severity": "error",
"human": "A Conformance statement SHALL have at least one of description, software, or implementation",
"xpath": "count(f:software | f:implementation | f:description) > 0"
},
{
"key": "cnf-4",
"name": "End point populated when multiple",
"severity": "error",
"human": "If there is more than one messaging element, endpoint must be specified for each one",
"xpath": "count(f:messaging)<=1 or not(f:messaging[not(f:endpoint)])"
},
{
"key": "cnf-5",
"name": "Messaging endpoints unique",
"severity": "error",
"human": "The set of end points listed for messaging must be unique",
"xpath": "count(f:messaging/f:endpoint)=count(distinct-values(f:messaging/f:endpoint/@value))"
},
{
"key": "cnf-7",
"name": "Document unique",
"severity": "error",
"human": "The set of documents must be unique by the combination of profile & mode",
"xpath": "count(f:document[f:mode='producer'])=count(distinct-values(f:document[f:mode='producer']/f:profile/@value)) and count(f:document[f:mode='consumer'])=count(distinct-values(f:document[f:mode='consumer']/f:profile/@value))"
},
{
"key": "cnf-8",
"name": "Rest unique by mode",
"severity": "error",
"human": "There can only be one REST declaration per mode",
"xpath": "count(f:rest)=count(distinct-values(f:rest/f:mode/@value))"
}
]
},
{
"path": "Conformance.id",
"short": "Logical id of this artefact",
"definition": "The logical id of the resource, as used in the url for the resoure. Once assigned, this value never changes.",
"comments": "The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
]
},
{
"path": "Conformance.meta",
"short": "Metadata about the resource",
"definition": "The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.",
"min": 0,
"max": "1",
"type": [
{
"code": "Meta"
}
]
},
{
"path": "Conformance.implicitRules",
"short": "A set of rules under which this content was created",
"definition": "A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.",
"comments": "Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
],
"isModifier": true
},
{
"path": "Conformance.language",
"short": "Language of the resource content",
"definition": "The base language in which the resource is written.",
"comments": "Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource\n\nNot all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "Language",
"isExtensible": false,
"conformance": "required",
"description": "A human language",
"referenceUri": "http://tools.ietf.org/html/bcp47"
}
},
{
"path": "Conformance.text",
"short": "Text summary of the resource, for human interpretation",
"definition": "A human-readable narrative that contains a summary of the resource, and may 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. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.",
"comments": "Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.",
"synonym": [
"narrative",
"html",
"xhtml",
"display"
],
"min": 0,
"max": "1",
"type": [
{
"code": "Narrative"
}
],
"condition": [
"dom-1"
],
"mapping": [
{
"identity": "rim",
"map": "Act.text?"
}
]
},
{
"path": "Conformance.contained",
"short": "Contained, inline Resources",
"definition": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
"comments": "This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.",
"synonym": [
"inline resources",
"anonymous resources",
"contained resources"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Resource"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.url",
"short": "Logical uri to reference this statement",
"definition": "The uri that is used to identify this conformance statement when it is referenced in a specification, model, design or an instance (should be globally unique URI, and an be urn:uuid: or urn:oid:).",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
],
"isSummary": true
},
{
"path": "Conformance.version",
"short": "Logical id for this version of the statement",
"definition": "The identifier that is used to identify this version of the conformance statement when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the profile author manually and the value should be a timestamp.",
"comments": "There may be multiple different instances of a conformance statement that have the same identifier but different versions.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.name",
"short": "Informal name for this conformance statement",
"definition": "A free text natural language name identifying the conformance statement.",
"comments": "The name is not expected to be globally unique.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.publisher",
"short": "Name of the publisher (Organization or individual)",
"definition": "The name of the individual or organization that published the conformance.",
"comments": "Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.",
"requirements": "Helps establish the \"authority/credibility\" of the conformance. May also allow for contact.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.contact",
"short": "Contact details of the publisher",
"definition": "Contacts to assist a user in finding and communicating with the publisher.",
"comments": "May be a web site, an email address, a telephone number (tel:), etc.",
"min": 0,
"max": "*",
"isSummary": true
},
{
"path": "Conformance.contact.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.contact.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.contact.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.contact.name",
"short": "Name of a individual to contact",
"definition": "The name of an individual to contact regarding the conformance.",
"comments": "If there is no named individual, the telecom is for the organization as a whole.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.contact.telecom",
"short": "Contact details for individual or publisher",
"definition": "Contact details for individual (if a name was provided) or the publisher.",
"min": 0,
"max": "*",
"type": [
{
"code": "ContactPoint"
}
],
"isSummary": true
},
{
"path": "Conformance.description",
"short": "Human description of the conformance statement",
"definition": "A free text natural language description of the conformance statement and its use. Typically, this is used when the profile describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP.",
"comments": "This field cmay include the purpose of this conformance statement, comments about its context etc. This does not need to be populated if the description is adequately implied by the software or implementation details.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"condition": [
"cnf-2"
],
"isSummary": true
},
{
"path": "Conformance.requirements",
"short": "Why is this needed?",
"definition": "Explains why this conformance statement is needed and why it's been constrained as it has.",
"comments": "This element does not describe the usage of the conformance statement (that's done in comments), rather it's for traceability of *why* the element is either needed or why the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this data element.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.copyright",
"short": "Use and/or Publishing restrictions",
"definition": "A copyright statement relating to the conformamce statement and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the details of the system described by the conformance statement.",
"synonym": [
"License",
"Restrictions"
],
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.status",
"short": "draft | active | retired",
"definition": "The status of this conformance statement.",
"comments": "This is not intended for use with actual conformance statements, but where conformance statements are used to describe possible or desired systems.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"isModifier": true,
"isSummary": true,
"binding": {
"name": "ConformanceStatementStatus",
"isExtensible": false,
"conformance": "required",
"description": "The status of this conformance statement",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/conformance-statement-status"
}
}
},
{
"path": "Conformance.experimental",
"short": "If for testing purposes, not real usage",
"definition": "A flag to indicate that this conformance statement is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.",
"comments": "Allows filtering of conformance statements that are appropriate for use vs. not.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
],
"isSummary": true
},
{
"path": "Conformance.date",
"short": "Publication Date(/time)",
"definition": "The date (and optionally time) when the conformance statement was published.",
"min": 1,
"max": "1",
"type": [
{
"code": "dateTime"
}
],
"isSummary": true
},
{
"path": "Conformance.software",
"short": "Software that is covered by this conformance statement",
"definition": "Software that is covered by this conformance statement. It is used when the profile describes the capabilities of a particular software version, independent of an installation.",
"min": 0,
"max": "1",
"condition": [
"cnf-2"
],
"isSummary": true
},
{
"path": "Conformance.software.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.software.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.software.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.software.name",
"short": "A name the software is known by",
"definition": "Name software is known by.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.software.version",
"short": "Version covered by this statement",
"definition": "The version identifier for the software covered by this statement.",
"comments": "If possible, version should be specified, as statements are likely to be different for different versions of software.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.software.releaseDate",
"short": "Date this version released",
"definition": "Date this version of the software released.",
"min": 0,
"max": "1",
"type": [
{
"code": "dateTime"
}
],
"isSummary": true
},
{
"path": "Conformance.implementation",
"short": "If this describes a specific instance",
"definition": "Identifies a specific implementation instance that is described by the conformance statement - i.e. a particular installation, rather than the capabilities of a software program.",
"min": 0,
"max": "1",
"condition": [
"cnf-2"
],
"isSummary": true
},
{
"path": "Conformance.implementation.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.implementation.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.implementation.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.implementation.description",
"short": "Describes this specific instance",
"definition": "Information about the specific installation that this conformance statement relates to.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.implementation.url",
"short": "Base URL for the installation",
"definition": "A base URL for the implementation. This forms the base for REST interfaces as well as the mailbox and document interfaces.",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
],
"isSummary": true
},
{
"path": "Conformance.fhirVersion",
"short": "FHIR Version",
"definition": "The version of the FHIR specification on which this conformance statement is based.",
"min": 1,
"max": "1",
"type": [
{
"code": "id"
}
],
"isSummary": true
},
{
"path": "Conformance.acceptUnknown",
"short": "True if application accepts unknown elements",
"definition": "A flag that indicates whether the application accepts unknown elements as part of a resource.",
"comments": "This is not about extensions, but about unknown elements in a resource - these can only arise as later versions of the specification are published, because this is the only place where such elements can be defined. Hence this element is about inter-version compatibility.",
"min": 1,
"max": "1",
"type": [
{
"code": "boolean"
}
],
"isSummary": true
},
{
"path": "Conformance.format",
"short": "formats supported (xml | json | mime type)",
"definition": "A list of the formats supported by this implementation.",
"comments": "\"xml\" or \"json\" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.",
"min": 1,
"max": "*",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "MimeType",
"isExtensible": false,
"conformance": "required",
"description": "The mime type of an attachment",
"referenceUri": "http://www.rfc-editor.org/bcp/bcp13.txt"
}
},
{
"path": "Conformance.profile",
"short": "Profiles supported by the system",
"definition": "A list of profiles supported by the system. For a server, \"supported by the system\" means the system hosts/produces a set of resources, conformant to a particular profile, and allows its clients to search using this profile and to find appropriate data. For a client, it means the system will search by this profile and process data according to the guidance implicit in the profile.",
"comments": "Supported profiles are different to the profiles that apply to a particular resource in rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports- this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that does? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile).\n\nTypical supported profiles cross resource types to describe a network of related resources, so they are listed here rather than by resource. However they do not need to describe more than one resource.",
"min": 0,
"max": "*",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.rest",
"short": "If the endpoint is a RESTful one",
"definition": "A definition of the restful capabilities of the solution, if any.",
"comments": "Multiple repetitions allow definition of both client and / or server behaviors or possibly behaviors under different configuration settings (for software or requirements statements).",
"min": 0,
"max": "*",
"condition": [
"cnf-1"
],
"constraint": [
{
"key": "cnf-10",
"name": "Query unique in rest mode",
"severity": "error",
"human": "A given query can only be described once per RESTful mode",
"xpath": "count(f:query)=count(distinct-values(f:query/f:name/@value))"
},
{
"key": "cnf-9",
"name": "Resource unique in rest mode",
"severity": "error",
"human": "A given resource can only be described once per RESTful mode",
"xpath": "count(f:resource)=count(distinct-values(f:resource/f:type/@value))"
}
]
},
{
"path": "Conformance.rest.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.mode",
"short": "client | server",
"definition": "Identifies whether this portion of the statement is describing ability to initiate or receive restful operations.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "RestfulConformanceMode",
"isExtensible": false,
"conformance": "required",
"description": "The mode of a RESTful conformance statement",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/restful-conformance-mode"
}
}
},
{
"path": "Conformance.rest.documentation",
"short": "General description of implementation",
"definition": "Information about the system's restful capabilities that apply across all applications, such as security.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.security",
"short": "Information about security of implementation",
"definition": "Information about security of implementation.",
"min": 0,
"max": "1"
},
{
"path": "Conformance.rest.security.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.security.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.security.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.security.cors",
"short": "Adds CORS Headers (http://enable-cors.org/)",
"definition": "Server adds CORS headers when responding to requests - this enables javascript applications to use the server.",
"comments": "The easiest CORS headers to add are Access-Control-Allow-Origin: * & Access-Control-Request-Method: GET, POST, PUT, DELETE.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.security.service",
"short": "OAuth | OAuth2 | NTLM | Basic | Kerberos",
"definition": "Types of security services are supported/required by the system.",
"min": 0,
"max": "*",
"type": [
{
"code": "CodeableConcept"
}
],
"binding": {
"name": "RestfulSecurityService",
"isExtensible": true,
"conformance": "preferred",
"description": "Types of security services used with FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/restful-security-service"
}
}
},
{
"path": "Conformance.rest.security.description",
"short": "General description of how security works",
"definition": "General description of how security works.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.security.certificate",
"short": "Certificates associated with security profiles",
"definition": "Certificates associated with security profiles.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.security.certificate.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.security.certificate.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.security.certificate.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.security.certificate.type",
"short": "Mime type for certificate",
"definition": "Mime type for certificate.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "MimeType",
"isExtensible": false,
"conformance": "required",
"description": "The mime type of an attachment",
"referenceUri": "http://www.rfc-editor.org/bcp/bcp13.txt"
}
},
{
"path": "Conformance.rest.security.certificate.blob",
"short": "Actual certificate",
"definition": "Actual certificate.",
"min": 0,
"max": "1",
"type": [
{
"code": "base64Binary"
}
]
},
{
"path": "Conformance.rest.resource",
"short": "Resource served on the REST interface",
"definition": "A specification of the restful capabilities of the solution for a specific resource type.",
"comments": "Max of one repetition per resource type.",
"min": 1,
"max": "*",
"constraint": [
{
"key": "cnf-12",
"name": "SearchParam unique in resource",
"severity": "error",
"human": "Search parameter names must be unique in the context of a resource",
"xpath": "count(f:searchParam)=count(distinct-values(f:searchParam/f:name/@value))"
},
{
"key": "cnf-11",
"name": "Operation unique in resource",
"severity": "error",
"human": "Operation codes must be unique in the context of a resource",
"xpath": "count(f:operation)=count(distinct-values(f:operation/f:code/@value))"
}
]
},
{
"path": "Conformance.rest.resource.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.resource.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.resource.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.resource.type",
"short": "A resource type that is supported",
"definition": "A type of resource exposed via the restful interface.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceType",
"isExtensible": false,
"conformance": "required",
"description": "One of the resource types defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/resource-types"
}
}
},
{
"path": "Conformance.rest.resource.profile",
"short": "What structural features are supported",
"definition": "A specification of the profile that describes the solution's support for the resource, including any constraints on cardinality, bindings, lengths or other limitations.",
"comments": "The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.",
"min": 0,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.rest.resource.interaction",
"short": "What operations are supported?",
"definition": "Identifies a restful operation supported by the solution.",
"min": 1,
"max": "*"
},
{
"path": "Conformance.rest.resource.interaction.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.resource.interaction.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.resource.interaction.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.resource.interaction.code",
"short": "read | vread | update | delete | history-instance | validate | history-type | create | search-type",
"definition": "Coded identifier of the operation, supported by the system resource.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "TypeRestfulInteraction",
"isExtensible": false,
"conformance": "required",
"description": "Operations supported by REST at the type or instance level",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/type-restful-interaction"
}
}
},
{
"path": "Conformance.rest.resource.interaction.documentation",
"short": "Anything special about operation behavior",
"definition": "Guidance specific to the implementation of this operation, such as 'delete is a logical delete' or 'updates are only allowed with version id' or 'creates permitted from pre-authorized certificates only'.",
"requirements": "REST allows a degree of variability in the implementation of RESTful solutions that is useful for exchange partners to be aware of.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.versioning",
"short": "no-version | versioned | versioned-update",
"definition": "Thi field is set to true to specify that the system does not support (server) or use (client) versioning for this resource type. If this is not set to true, the server must at least correctly track and populate the versionId meta-property on resources.",
"comments": "If a server supports versionIds correctly, it should support vread too, but is not required to do so.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceVersionPolicy",
"isExtensible": false,
"conformance": "required",
"description": "How the system supports versioning for a resource",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/versioning-policy"
}
}
},
{
"path": "Conformance.rest.resource.readHistory",
"short": "Whether vRead can return past versions",
"definition": "A flag for whether the server is able to return past versions as part of the vRead operation.",
"comments": "It is useful to support the vRead operation for current operations, even if past versions aren't available.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.updateCreate",
"short": "If allows/uses update to a new location",
"definition": "A flag to indicate that the server allows the client to create new identities on the server. If the update operation is used (client) or allowed (server) to a new location where a resource doesn't already exist. This means that the server allows the client to create new identities on the server.",
"comments": "Allowing the clients to create new identities on the server means that the system administrator needs to have confidence that the clients do not create clashing identities between them. Obviously, if there is only one client, this won't happen. While creating identities on the client means that the clients need to be managed, it's much more convenient for many scenarios.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.conditionalCreate",
"short": "If allows/uses conditional create",
"definition": "A flag that indicates that the server supports conditional create.",
"comments": "Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.conditionalUpdate",
"short": "If allows/uses conditional update",
"definition": "A flag that indicates that the server supports conditional update.",
"comments": "Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.conditionalDelete",
"short": "If allows/uses conditional delete",
"definition": "A flag that indicates that the server supports conditional delete.",
"comments": "Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.searchInclude",
"short": "_include values supported by the server",
"definition": "A list of _include values supported by the server.",
"comments": "If this list is empty, the server does not support includes.",
"min": 0,
"max": "*",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.searchParam",
"short": "Search params supported by implementation",
"definition": "Search parameters for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.resource.searchParam.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.name",
"short": "Name of search parameter",
"definition": "The name of the search parameter used in the interface.",
"comments": "Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.definition",
"short": "Source of definition for parameter",
"definition": "A formal reference to where this parameter was first defined, so that a client can be confident of the meaning of the search parameter.",
"comments": "This SHOULD be present, and matches SearchParameter.url.",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.type",
"short": "number | date | string | token | reference | composite | quantity",
"definition": "The type of value a search parameter refers to, and how the content is interpreted.",
"comments": "While this can be looked up from the definition, it is included here as a convenience for systems that auto-generate a query interface based on the server conformance statement. It SHALL be the same as the type in the search parameter definition.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "SearchParamType",
"isExtensible": false,
"conformance": "required",
"description": "Data types allowed to be used for search parameters",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/search-param-type"
}
}
},
{
"path": "Conformance.rest.resource.searchParam.documentation",
"short": "Server-specific usage",
"definition": "This allows documentation of any distinct behaviors about how the search parameter is used. For example, text matching algorithms.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.target",
"short": "Types of resource (if a resource reference)",
"definition": "Types of resource (if a resource is referenced).",
"comments": "This SHALL be the same as or a proper subset of the resources listed in the search parameter definition.",
"min": 0,
"max": "*",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceType",
"isExtensible": false,
"conformance": "required",
"description": "One of the resource types defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/resource-types"
}
}
},
{
"path": "Conformance.rest.resource.searchParam.chain",
"short": "Chained names supported",
"definition": "Chained names supported.",
"min": 0,
"max": "*",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.interaction",
"short": "What operations are supported?",
"definition": "A specification of restful operations supported by the system.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.interaction.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.interaction.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.interaction.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.interaction.code",
"short": "transaction | search-system | history-system",
"definition": "A coded identifier of the operation, supported by the system.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "SystemRestfulInteraction",
"isExtensible": false,
"conformance": "required",
"description": "Operations supported by REST at the system level",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/system-restful-interaction"
}
}
},
{
"path": "Conformance.rest.interaction.documentation",
"short": "Anything special about operation behavior",
"definition": "Guidance specific to the implementation of this operation, such as limitations on the kind of transactions allowed, or information about system wide search is implemented.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.operation",
"short": "Definition of an operation or a custom query",
"definition": "Definition of an operation or a named query and with its parameters and their meaning and type.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.operation.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.operation.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.rest.operation.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.rest.operation.name",
"short": "Name by which the operation/query is invoked",
"definition": "The name of a query, which is used in the _query parameter when the query is called.",
"comments": "The name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.operation.definition",
"short": "The defined operation/query",
"definition": "Where the formal definition can be found.",
"comments": "This can be used to build ah HTML form to invoke the operation, for instance.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/OperationDefinition"
}
]
},
{
"path": "Conformance.rest.documentMailbox",
"short": "How documents are accepted in /Mailbox",
"definition": "A list of profiles that this server implements for accepting documents in the mailbox. If this list is empty, then documents are not accepted. The base specification has the profile identifier \"http://hl7.org/fhir/documents/mailbox\". Other specifications can declare their own identifier for this purpose.",
"comments": "If a server accepts messages on the /Mailbox end-point, it declares this in the messaging elements.",
"min": 0,
"max": "*",
"type": [
{
"code": "uri"
}
]
},
{
"path": "Conformance.messaging",
"short": "If messaging is supported",
"definition": "A description of the messaging capabilities of the solution.",
"comments": "Multiple repetitions allow the documentation of multiple endpoints per solution.",
"min": 0,
"max": "*",
"condition": [
"cnf-1"
],
"constraint": [
{
"key": "cnf-3",
"name": "End points for Implementations",
"severity": "error",
"human": "Messaging end point is required (and is only permitted) when statement is for an implementation",
"xpath": "exists(f:endpoint) = exists(parent::f:Conformance/f:implementation)"
},
{
"key": "cnf-6",
"name": "Event unique",
"severity": "error",
"human": "The set of events per messaging endpoint must be unique by the combination of code & mode",
"xpath": "count(f:event[f:mode='sender'])=count(distinct-values(f:event[f:mode='sender']/f:code/@value)) and count(f:event[f:mode='receiver'])=count(distinct-values(f:event[f:mode='receiver']/f:code/@value))"
}
]
},
{
"path": "Conformance.messaging.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.messaging.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.messaging.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.messaging.endpoint",
"short": "Actual endpoint being described",
"definition": "An address to which messages and/or replies are to be sent.",
"comments": "For solutions that do not use network addresses for routing, it can be just an identifier.",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
],
"condition": [
"cnf-3"
]
},
{
"path": "Conformance.messaging.reliableCache",
"short": "Reliable Message Cache Length (min)",
"definition": "Length if the receiver's reliable messaging cache in minutes (if a receiver) or how long the cache length on the receiver should be (if a sender).",
"comments": "If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging.",
"min": 0,
"max": "1",
"type": [
{
"code": "integer"
}
]
},
{
"path": "Conformance.messaging.documentation",
"short": "Messaging interface behavior details",
"definition": "Documentation about the system's messaging capabilities for this endpoint not otherwise documented by the conformance statement. For example, process for becoming an authorized messaging exchange partner.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.messaging.event",
"short": "Declare support for this event",
"definition": "A description of the solution's support for an event at this end point.",
"comments": "The same event may be listed up to two times - once as sender and once as receiver.",
"min": 1,
"max": "*"
},
{
"path": "Conformance.messaging.event.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.messaging.event.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.messaging.event.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.messaging.event.code",
"short": "Event type",
"definition": "A coded identifier of a supported messaging event.",
"min": 1,
"max": "1",
"type": [
{
"code": "Coding"
}
],
"binding": {
"name": "MessageEvent",
"isExtensible": true,
"conformance": "preferred",
"description": "One of the message events defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-events"
}
}
},
{
"path": "Conformance.messaging.event.category",
"short": "Consequence | Currency | Notification",
"definition": "The impact of the content of the message.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "MessageSignificanceCategory",
"isExtensible": false,
"conformance": "required",
"description": "The impact of the content of a message",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-significance-category"
}
}
},
{
"path": "Conformance.messaging.event.mode",
"short": "sender | receiver",
"definition": "The mode of this event declaration - whether application is sender or receiver.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ConformanceEventMode",
"isExtensible": false,
"conformance": "required",
"description": "The mode of a message conformance statement",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-conformance-event-mode"
}
}
},
{
"path": "Conformance.messaging.event.protocol",
"short": "http | ftp | mllp +",
"definition": "A list of the messaging transport protocol(s) identifiers, supported by this endpoint.",
"min": 0,
"max": "*",
"type": [
{
"code": "Coding"
}
],
"binding": {
"name": "MessageTransport",
"isExtensible": true,
"conformance": "preferred",
"description": "The protocol used for message transport",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-transport"
}
}
},
{
"path": "Conformance.messaging.event.focus",
"short": "Resource that's focus of message",
"definition": "A resource associated with the event. This is the resource that defines the event.",
"comments": "This SHALL be provided if the event type supports multiple different resource types.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceType",
"isExtensible": false,
"conformance": "required",
"description": "One of the resource types defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/resource-types"
}
}
},
{
"path": "Conformance.messaging.event.request",
"short": "Profile that describes the request",
"definition": "Information about the request for this event.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.messaging.event.response",
"short": "Profile that describes the response",
"definition": "Information about the response for this event.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.messaging.event.documentation",
"short": "Endpoint-specific event documentation",
"definition": "Guidance on how this event is handled, such as internal system trigger points, business rules, etc.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.document",
"short": "Document definition",
"definition": "A document definition.",
"min": 0,
"max": "*",
"condition": [
"cnf-1"
]
},
{
"path": "Conformance.document.id",
"representation": [
"xmlAttr"
],
"short": "xml:id (or equivalent in JSON)",
"definition": "unique id for the element within a resource (for internal references).",
"min": 0,
"max": "1",
"type": [
{
"code": "id"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.document.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "n/a"
}
]
},
{
"path": "Conformance.document.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"synonym": [
"extensions",
"user content",
"modifiers"
],
"min": 0,
"max": "*",
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "Conformance.document.mode",
"short": "producer | consumer",
"definition": "Mode of this document declaration - whether application is producer or consumer.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "DocumentMode",
"isExtensible": false,
"conformance": "required",
"description": "Whether the application produces or consumes documents",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/document-mode"
}
}
},
{
"path": "Conformance.document.documentation",
"short": "Description of document support",
"definition": "A description of how the application supports or uses the specified document profile. For example, when are documents created, what action is taken with consumed documents, etc.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.document.profile",
"short": "Constraint on a resource used in the document",
"definition": "A constraint on a resource used in the document.",
"comments": "The first resource is the document resource.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
}
]
},
"differential": {
"element": [
{
"path": "Conformance",
"short": "A conformance statement",
"definition": "A conformance statement is a set of requirements for a desired implementation or a description of how a target application fulfills those requirements in a particular implementation.",
"min": 1,
"max": "1",
"constraint": [
{
"key": "cnf-1",
"name": "Content Required",
"severity": "error",
"human": "A Conformance statement SHALL have at least one of rest, messaging or document",
"xpath": "exists(f:rest) or exists(f:messaging) or exists(f:document)"
},
{
"key": "cnf-2",
"name": "Details",
"severity": "error",
"human": "A Conformance statement SHALL have at least one of description, software, or implementation",
"xpath": "count(f:software | f:implementation | f:description) > 0"
},
{
"key": "cnf-4",
"name": "End point populated when multiple",
"severity": "error",
"human": "If there is more than one messaging element, endpoint must be specified for each one",
"xpath": "count(f:messaging)<=1 or not(f:messaging[not(f:endpoint)])"
},
{
"key": "cnf-5",
"name": "Messaging endpoints unique",
"severity": "error",
"human": "The set of end points listed for messaging must be unique",
"xpath": "count(f:messaging/f:endpoint)=count(distinct-values(f:messaging/f:endpoint/@value))"
},
{
"key": "cnf-7",
"name": "Document unique",
"severity": "error",
"human": "The set of documents must be unique by the combination of profile & mode",
"xpath": "count(f:document[f:mode='producer'])=count(distinct-values(f:document[f:mode='producer']/f:profile/@value)) and count(f:document[f:mode='consumer'])=count(distinct-values(f:document[f:mode='consumer']/f:profile/@value))"
},
{
"key": "cnf-8",
"name": "Rest unique by mode",
"severity": "error",
"human": "There can only be one REST declaration per mode",
"xpath": "count(f:rest)=count(distinct-values(f:rest/f:mode/@value))"
}
]
},
{
"path": "Conformance.url",
"short": "Logical uri to reference this statement",
"definition": "The uri that is used to identify this conformance statement when it is referenced in a specification, model, design or an instance (should be globally unique URI, and an be urn:uuid: or urn:oid:).",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
],
"isSummary": true
},
{
"path": "Conformance.version",
"short": "Logical id for this version of the statement",
"definition": "The identifier that is used to identify this version of the conformance statement when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the profile author manually and the value should be a timestamp.",
"comments": "There may be multiple different instances of a conformance statement that have the same identifier but different versions.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.name",
"short": "Informal name for this conformance statement",
"definition": "A free text natural language name identifying the conformance statement.",
"comments": "The name is not expected to be globally unique.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.publisher",
"short": "Name of the publisher (Organization or individual)",
"definition": "The name of the individual or organization that published the conformance.",
"comments": "Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.",
"requirements": "Helps establish the \"authority/credibility\" of the conformance. May also allow for contact.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.contact",
"short": "Contact details of the publisher",
"definition": "Contacts to assist a user in finding and communicating with the publisher.",
"comments": "May be a web site, an email address, a telephone number (tel:), etc.",
"min": 0,
"max": "*",
"isSummary": true
},
{
"path": "Conformance.contact.name",
"short": "Name of a individual to contact",
"definition": "The name of an individual to contact regarding the conformance.",
"comments": "If there is no named individual, the telecom is for the organization as a whole.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.contact.telecom",
"short": "Contact details for individual or publisher",
"definition": "Contact details for individual (if a name was provided) or the publisher.",
"min": 0,
"max": "*",
"type": [
{
"code": "ContactPoint"
}
],
"isSummary": true
},
{
"path": "Conformance.description",
"short": "Human description of the conformance statement",
"definition": "A free text natural language description of the conformance statement and its use. Typically, this is used when the profile describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP.",
"comments": "This field cmay include the purpose of this conformance statement, comments about its context etc. This does not need to be populated if the description is adequately implied by the software or implementation details.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"condition": [
"cnf-2"
],
"isSummary": true
},
{
"path": "Conformance.requirements",
"short": "Why is this needed?",
"definition": "Explains why this conformance statement is needed and why it's been constrained as it has.",
"comments": "This element does not describe the usage of the conformance statement (that's done in comments), rather it's for traceability of *why* the element is either needed or why the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this data element.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.copyright",
"short": "Use and/or Publishing restrictions",
"definition": "A copyright statement relating to the conformamce statement and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the details of the system described by the conformance statement.",
"synonym": [
"License",
"Restrictions"
],
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.status",
"short": "draft | active | retired",
"definition": "The status of this conformance statement.",
"comments": "This is not intended for use with actual conformance statements, but where conformance statements are used to describe possible or desired systems.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"isModifier": true,
"isSummary": true,
"binding": {
"name": "ConformanceStatementStatus",
"isExtensible": false,
"conformance": "required",
"description": "The status of this conformance statement",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/conformance-statement-status"
}
}
},
{
"path": "Conformance.experimental",
"short": "If for testing purposes, not real usage",
"definition": "A flag to indicate that this conformance statement is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.",
"comments": "Allows filtering of conformance statements that are appropriate for use vs. not.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
],
"isSummary": true
},
{
"path": "Conformance.date",
"short": "Publication Date(/time)",
"definition": "The date (and optionally time) when the conformance statement was published.",
"min": 1,
"max": "1",
"type": [
{
"code": "dateTime"
}
],
"isSummary": true
},
{
"path": "Conformance.software",
"short": "Software that is covered by this conformance statement",
"definition": "Software that is covered by this conformance statement. It is used when the profile describes the capabilities of a particular software version, independent of an installation.",
"min": 0,
"max": "1",
"condition": [
"cnf-2"
],
"isSummary": true
},
{
"path": "Conformance.software.name",
"short": "A name the software is known by",
"definition": "Name software is known by.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.software.version",
"short": "Version covered by this statement",
"definition": "The version identifier for the software covered by this statement.",
"comments": "If possible, version should be specified, as statements are likely to be different for different versions of software.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.software.releaseDate",
"short": "Date this version released",
"definition": "Date this version of the software released.",
"min": 0,
"max": "1",
"type": [
{
"code": "dateTime"
}
],
"isSummary": true
},
{
"path": "Conformance.implementation",
"short": "If this describes a specific instance",
"definition": "Identifies a specific implementation instance that is described by the conformance statement - i.e. a particular installation, rather than the capabilities of a software program.",
"min": 0,
"max": "1",
"condition": [
"cnf-2"
],
"isSummary": true
},
{
"path": "Conformance.implementation.description",
"short": "Describes this specific instance",
"definition": "Information about the specific installation that this conformance statement relates to.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
],
"isSummary": true
},
{
"path": "Conformance.implementation.url",
"short": "Base URL for the installation",
"definition": "A base URL for the implementation. This forms the base for REST interfaces as well as the mailbox and document interfaces.",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
],
"isSummary": true
},
{
"path": "Conformance.fhirVersion",
"short": "FHIR Version",
"definition": "The version of the FHIR specification on which this conformance statement is based.",
"min": 1,
"max": "1",
"type": [
{
"code": "id"
}
],
"isSummary": true
},
{
"path": "Conformance.acceptUnknown",
"short": "True if application accepts unknown elements",
"definition": "A flag that indicates whether the application accepts unknown elements as part of a resource.",
"comments": "This is not about extensions, but about unknown elements in a resource - these can only arise as later versions of the specification are published, because this is the only place where such elements can be defined. Hence this element is about inter-version compatibility.",
"min": 1,
"max": "1",
"type": [
{
"code": "boolean"
}
],
"isSummary": true
},
{
"path": "Conformance.format",
"short": "formats supported (xml | json | mime type)",
"definition": "A list of the formats supported by this implementation.",
"comments": "\"xml\" or \"json\" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.",
"min": 1,
"max": "*",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "MimeType",
"isExtensible": false,
"conformance": "required",
"description": "The mime type of an attachment",
"referenceUri": "http://www.rfc-editor.org/bcp/bcp13.txt"
}
},
{
"path": "Conformance.profile",
"short": "Profiles supported by the system",
"definition": "A list of profiles supported by the system. For a server, \"supported by the system\" means the system hosts/produces a set of resources, conformant to a particular profile, and allows its clients to search using this profile and to find appropriate data. For a client, it means the system will search by this profile and process data according to the guidance implicit in the profile.",
"comments": "Supported profiles are different to the profiles that apply to a particular resource in rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports- this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that does? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile).\n\nTypical supported profiles cross resource types to describe a network of related resources, so they are listed here rather than by resource. However they do not need to describe more than one resource.",
"min": 0,
"max": "*",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.rest",
"short": "If the endpoint is a RESTful one",
"definition": "A definition of the restful capabilities of the solution, if any.",
"comments": "Multiple repetitions allow definition of both client and / or server behaviors or possibly behaviors under different configuration settings (for software or requirements statements).",
"min": 0,
"max": "*",
"condition": [
"cnf-1"
],
"constraint": [
{
"key": "cnf-10",
"name": "Query unique in rest mode",
"severity": "error",
"human": "A given query can only be described once per RESTful mode",
"xpath": "count(f:query)=count(distinct-values(f:query/f:name/@value))"
},
{
"key": "cnf-9",
"name": "Resource unique in rest mode",
"severity": "error",
"human": "A given resource can only be described once per RESTful mode",
"xpath": "count(f:resource)=count(distinct-values(f:resource/f:type/@value))"
}
]
},
{
"path": "Conformance.rest.mode",
"short": "client | server",
"definition": "Identifies whether this portion of the statement is describing ability to initiate or receive restful operations.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "RestfulConformanceMode",
"isExtensible": false,
"conformance": "required",
"description": "The mode of a RESTful conformance statement",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/restful-conformance-mode"
}
}
},
{
"path": "Conformance.rest.documentation",
"short": "General description of implementation",
"definition": "Information about the system's restful capabilities that apply across all applications, such as security.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.security",
"short": "Information about security of implementation",
"definition": "Information about security of implementation.",
"min": 0,
"max": "1"
},
{
"path": "Conformance.rest.security.cors",
"short": "Adds CORS Headers (http://enable-cors.org/)",
"definition": "Server adds CORS headers when responding to requests - this enables javascript applications to use the server.",
"comments": "The easiest CORS headers to add are Access-Control-Allow-Origin: * & Access-Control-Request-Method: GET, POST, PUT, DELETE.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.security.service",
"short": "OAuth | OAuth2 | NTLM | Basic | Kerberos",
"definition": "Types of security services are supported/required by the system.",
"min": 0,
"max": "*",
"type": [
{
"code": "CodeableConcept"
}
],
"binding": {
"name": "RestfulSecurityService",
"isExtensible": true,
"conformance": "preferred",
"description": "Types of security services used with FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/restful-security-service"
}
}
},
{
"path": "Conformance.rest.security.description",
"short": "General description of how security works",
"definition": "General description of how security works.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.security.certificate",
"short": "Certificates associated with security profiles",
"definition": "Certificates associated with security profiles.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.security.certificate.type",
"short": "Mime type for certificate",
"definition": "Mime type for certificate.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "MimeType",
"isExtensible": false,
"conformance": "required",
"description": "The mime type of an attachment",
"referenceUri": "http://www.rfc-editor.org/bcp/bcp13.txt"
}
},
{
"path": "Conformance.rest.security.certificate.blob",
"short": "Actual certificate",
"definition": "Actual certificate.",
"min": 0,
"max": "1",
"type": [
{
"code": "base64Binary"
}
]
},
{
"path": "Conformance.rest.resource",
"short": "Resource served on the REST interface",
"definition": "A specification of the restful capabilities of the solution for a specific resource type.",
"comments": "Max of one repetition per resource type.",
"min": 1,
"max": "*",
"constraint": [
{
"key": "cnf-12",
"name": "SearchParam unique in resource",
"severity": "error",
"human": "Search parameter names must be unique in the context of a resource",
"xpath": "count(f:searchParam)=count(distinct-values(f:searchParam/f:name/@value))"
},
{
"key": "cnf-11",
"name": "Operation unique in resource",
"severity": "error",
"human": "Operation codes must be unique in the context of a resource",
"xpath": "count(f:operation)=count(distinct-values(f:operation/f:code/@value))"
}
]
},
{
"path": "Conformance.rest.resource.type",
"short": "A resource type that is supported",
"definition": "A type of resource exposed via the restful interface.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceType",
"isExtensible": false,
"conformance": "required",
"description": "One of the resource types defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/resource-types"
}
}
},
{
"path": "Conformance.rest.resource.profile",
"short": "What structural features are supported",
"definition": "A specification of the profile that describes the solution's support for the resource, including any constraints on cardinality, bindings, lengths or other limitations.",
"comments": "The profile applies to all resources of this type - i.e. it is the superset of what is supported by the system.",
"min": 0,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.rest.resource.interaction",
"short": "What operations are supported?",
"definition": "Identifies a restful operation supported by the solution.",
"min": 1,
"max": "*"
},
{
"path": "Conformance.rest.resource.interaction.code",
"short": "read | vread | update | delete | history-instance | validate | history-type | create | search-type",
"definition": "Coded identifier of the operation, supported by the system resource.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "TypeRestfulInteraction",
"isExtensible": false,
"conformance": "required",
"description": "Operations supported by REST at the type or instance level",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/type-restful-interaction"
}
}
},
{
"path": "Conformance.rest.resource.interaction.documentation",
"short": "Anything special about operation behavior",
"definition": "Guidance specific to the implementation of this operation, such as 'delete is a logical delete' or 'updates are only allowed with version id' or 'creates permitted from pre-authorized certificates only'.",
"requirements": "REST allows a degree of variability in the implementation of RESTful solutions that is useful for exchange partners to be aware of.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.versioning",
"short": "no-version | versioned | versioned-update",
"definition": "Thi field is set to true to specify that the system does not support (server) or use (client) versioning for this resource type. If this is not set to true, the server must at least correctly track and populate the versionId meta-property on resources.",
"comments": "If a server supports versionIds correctly, it should support vread too, but is not required to do so.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceVersionPolicy",
"isExtensible": false,
"conformance": "required",
"description": "How the system supports versioning for a resource",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/versioning-policy"
}
}
},
{
"path": "Conformance.rest.resource.readHistory",
"short": "Whether vRead can return past versions",
"definition": "A flag for whether the server is able to return past versions as part of the vRead operation.",
"comments": "It is useful to support the vRead operation for current operations, even if past versions aren't available.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.updateCreate",
"short": "If allows/uses update to a new location",
"definition": "A flag to indicate that the server allows the client to create new identities on the server. If the update operation is used (client) or allowed (server) to a new location where a resource doesn't already exist. This means that the server allows the client to create new identities on the server.",
"comments": "Allowing the clients to create new identities on the server means that the system administrator needs to have confidence that the clients do not create clashing identities between them. Obviously, if there is only one client, this won't happen. While creating identities on the client means that the clients need to be managed, it's much more convenient for many scenarios.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.conditionalCreate",
"short": "If allows/uses conditional create",
"definition": "A flag that indicates that the server supports conditional create.",
"comments": "Conditional Create is mainly appropriate for interface engine scripts converting from other formats, such as v2.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.conditionalUpdate",
"short": "If allows/uses conditional update",
"definition": "A flag that indicates that the server supports conditional update.",
"comments": "Conditional Update is mainly appropriate for interface engine scripts converting from other formats, such as v2.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.conditionalDelete",
"short": "If allows/uses conditional delete",
"definition": "A flag that indicates that the server supports conditional delete.",
"comments": "Conditional Delete is mainly appropriate for interface engine scripts converting from other formats, such as v2.",
"min": 0,
"max": "1",
"type": [
{
"code": "boolean"
}
]
},
{
"path": "Conformance.rest.resource.searchInclude",
"short": "_include values supported by the server",
"definition": "A list of _include values supported by the server.",
"comments": "If this list is empty, the server does not support includes.",
"min": 0,
"max": "*",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.searchParam",
"short": "Search params supported by implementation",
"definition": "Search parameters for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.resource.searchParam.name",
"short": "Name of search parameter",
"definition": "The name of the search parameter used in the interface.",
"comments": "Parameter names cannot overlap with standard parameter names, and standard parameters cannot be redefined.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.definition",
"short": "Source of definition for parameter",
"definition": "A formal reference to where this parameter was first defined, so that a client can be confident of the meaning of the search parameter.",
"comments": "This SHOULD be present, and matches SearchParameter.url.",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.type",
"short": "number | date | string | token | reference | composite | quantity",
"definition": "The type of value a search parameter refers to, and how the content is interpreted.",
"comments": "While this can be looked up from the definition, it is included here as a convenience for systems that auto-generate a query interface based on the server conformance statement. It SHALL be the same as the type in the search parameter definition.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "SearchParamType",
"isExtensible": false,
"conformance": "required",
"description": "Data types allowed to be used for search parameters",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/search-param-type"
}
}
},
{
"path": "Conformance.rest.resource.searchParam.documentation",
"short": "Server-specific usage",
"definition": "This allows documentation of any distinct behaviors about how the search parameter is used. For example, text matching algorithms.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.resource.searchParam.target",
"short": "Types of resource (if a resource reference)",
"definition": "Types of resource (if a resource is referenced).",
"comments": "This SHALL be the same as or a proper subset of the resources listed in the search parameter definition.",
"min": 0,
"max": "*",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceType",
"isExtensible": false,
"conformance": "required",
"description": "One of the resource types defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/resource-types"
}
}
},
{
"path": "Conformance.rest.resource.searchParam.chain",
"short": "Chained names supported",
"definition": "Chained names supported.",
"min": 0,
"max": "*",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.interaction",
"short": "What operations are supported?",
"definition": "A specification of restful operations supported by the system.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.interaction.code",
"short": "transaction | search-system | history-system",
"definition": "A coded identifier of the operation, supported by the system.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "SystemRestfulInteraction",
"isExtensible": false,
"conformance": "required",
"description": "Operations supported by REST at the system level",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/system-restful-interaction"
}
}
},
{
"path": "Conformance.rest.interaction.documentation",
"short": "Anything special about operation behavior",
"definition": "Guidance specific to the implementation of this operation, such as limitations on the kind of transactions allowed, or information about system wide search is implemented.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.operation",
"short": "Definition of an operation or a custom query",
"definition": "Definition of an operation or a named query and with its parameters and their meaning and type.",
"min": 0,
"max": "*"
},
{
"path": "Conformance.rest.operation.name",
"short": "Name by which the operation/query is invoked",
"definition": "The name of a query, which is used in the _query parameter when the query is called.",
"comments": "The name here SHOULD be the same as the name in the definition, unless there is a name clash and the name cannot be used.",
"min": 1,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.rest.operation.definition",
"short": "The defined operation/query",
"definition": "Where the formal definition can be found.",
"comments": "This can be used to build ah HTML form to invoke the operation, for instance.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/OperationDefinition"
}
]
},
{
"path": "Conformance.rest.documentMailbox",
"short": "How documents are accepted in /Mailbox",
"definition": "A list of profiles that this server implements for accepting documents in the mailbox. If this list is empty, then documents are not accepted. The base specification has the profile identifier \"http://hl7.org/fhir/documents/mailbox\". Other specifications can declare their own identifier for this purpose.",
"comments": "If a server accepts messages on the /Mailbox end-point, it declares this in the messaging elements.",
"min": 0,
"max": "*",
"type": [
{
"code": "uri"
}
]
},
{
"path": "Conformance.messaging",
"short": "If messaging is supported",
"definition": "A description of the messaging capabilities of the solution.",
"comments": "Multiple repetitions allow the documentation of multiple endpoints per solution.",
"min": 0,
"max": "*",
"condition": [
"cnf-1"
],
"constraint": [
{
"key": "cnf-3",
"name": "End points for Implementations",
"severity": "error",
"human": "Messaging end point is required (and is only permitted) when statement is for an implementation",
"xpath": "exists(f:endpoint) = exists(parent::f:Conformance/f:implementation)"
},
{
"key": "cnf-6",
"name": "Event unique",
"severity": "error",
"human": "The set of events per messaging endpoint must be unique by the combination of code & mode",
"xpath": "count(f:event[f:mode='sender'])=count(distinct-values(f:event[f:mode='sender']/f:code/@value)) and count(f:event[f:mode='receiver'])=count(distinct-values(f:event[f:mode='receiver']/f:code/@value))"
}
]
},
{
"path": "Conformance.messaging.endpoint",
"short": "Actual endpoint being described",
"definition": "An address to which messages and/or replies are to be sent.",
"comments": "For solutions that do not use network addresses for routing, it can be just an identifier.",
"min": 0,
"max": "1",
"type": [
{
"code": "uri"
}
],
"condition": [
"cnf-3"
]
},
{
"path": "Conformance.messaging.reliableCache",
"short": "Reliable Message Cache Length (min)",
"definition": "Length if the receiver's reliable messaging cache in minutes (if a receiver) or how long the cache length on the receiver should be (if a sender).",
"comments": "If this value is missing then the application does not implement (receiver) or depend on (sender) reliable messaging.",
"min": 0,
"max": "1",
"type": [
{
"code": "integer"
}
]
},
{
"path": "Conformance.messaging.documentation",
"short": "Messaging interface behavior details",
"definition": "Documentation about the system's messaging capabilities for this endpoint not otherwise documented by the conformance statement. For example, process for becoming an authorized messaging exchange partner.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.messaging.event",
"short": "Declare support for this event",
"definition": "A description of the solution's support for an event at this end point.",
"comments": "The same event may be listed up to two times - once as sender and once as receiver.",
"min": 1,
"max": "*"
},
{
"path": "Conformance.messaging.event.code",
"short": "Event type",
"definition": "A coded identifier of a supported messaging event.",
"min": 1,
"max": "1",
"type": [
{
"code": "Coding"
}
],
"binding": {
"name": "MessageEvent",
"isExtensible": true,
"conformance": "preferred",
"description": "One of the message events defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-events"
}
}
},
{
"path": "Conformance.messaging.event.category",
"short": "Consequence | Currency | Notification",
"definition": "The impact of the content of the message.",
"min": 0,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "MessageSignificanceCategory",
"isExtensible": false,
"conformance": "required",
"description": "The impact of the content of a message",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-significance-category"
}
}
},
{
"path": "Conformance.messaging.event.mode",
"short": "sender | receiver",
"definition": "The mode of this event declaration - whether application is sender or receiver.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ConformanceEventMode",
"isExtensible": false,
"conformance": "required",
"description": "The mode of a message conformance statement",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-conformance-event-mode"
}
}
},
{
"path": "Conformance.messaging.event.protocol",
"short": "http | ftp | mllp +",
"definition": "A list of the messaging transport protocol(s) identifiers, supported by this endpoint.",
"min": 0,
"max": "*",
"type": [
{
"code": "Coding"
}
],
"binding": {
"name": "MessageTransport",
"isExtensible": true,
"conformance": "preferred",
"description": "The protocol used for message transport",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/message-transport"
}
}
},
{
"path": "Conformance.messaging.event.focus",
"short": "Resource that's focus of message",
"definition": "A resource associated with the event. This is the resource that defines the event.",
"comments": "This SHALL be provided if the event type supports multiple different resource types.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "ResourceType",
"isExtensible": false,
"conformance": "required",
"description": "One of the resource types defined as part of FHIR",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/resource-types"
}
}
},
{
"path": "Conformance.messaging.event.request",
"short": "Profile that describes the request",
"definition": "Information about the request for this event.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.messaging.event.response",
"short": "Profile that describes the response",
"definition": "Information about the response for this event.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
},
{
"path": "Conformance.messaging.event.documentation",
"short": "Endpoint-specific event documentation",
"definition": "Guidance on how this event is handled, such as internal system trigger points, business rules, etc.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.document",
"short": "Document definition",
"definition": "A document definition.",
"min": 0,
"max": "*",
"condition": [
"cnf-1"
]
},
{
"path": "Conformance.document.mode",
"short": "producer | consumer",
"definition": "Mode of this document declaration - whether application is producer or consumer.",
"min": 1,
"max": "1",
"type": [
{
"code": "code"
}
],
"binding": {
"name": "DocumentMode",
"isExtensible": false,
"conformance": "required",
"description": "Whether the application produces or consumes documents",
"referenceReference": {
"reference": "http://hl7.org/fhir/vs/document-mode"
}
}
},
{
"path": "Conformance.document.documentation",
"short": "Description of document support",
"definition": "A description of how the application supports or uses the specified document profile. For example, when are documents created, what action is taken with consumed documents, etc.",
"min": 0,
"max": "1",
"type": [
{
"code": "string"
}
]
},
{
"path": "Conformance.document.profile",
"short": "Constraint on a resource used in the document",
"definition": "A constraint on a resource used in the document.",
"comments": "The first resource is the document resource.",
"min": 1,
"max": "1",
"type": [
{
"code": "Reference",
"profile": "http://hl7.org/fhir/Profile/Profile"
}
]
}
]
}
}
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.
© HL7.org 2011+. FHIR DSTU (v0.4.0-4167) generated on Mon, Feb 23, 2015 09:19+1100.
Links: What's a DSTU? |
Version History |
Compare to DSTU1 |
|
Propose a change