StructureDefinition: C-CDA on FHIR Authorization

STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

M.??.3 StructureDefinition: C-CDA on FHIR Authorization - Detailed Descriptions

Definitions for the ccda-authorization-extension Profile.

Extension
Definition	An Extension
Control	0..*
Type	Element
Extension.id
Definition	unique id for the element within a resource (for internal references).
Control	0..1
Type	id
Extension.extension
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.
Control	0..*
Type	Extension
Alternate Names	extensions, user content
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.
Extension.url
Definition	SHALL contain exactly one [1..1] @url="http://hl7.org/fhir/StructureDefinition/ccda-authorization-extension" (CONF:2219-2010).
Control	1..1
Type	uri
Comments	The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.
Extension.value[x]
Definition	SHALL contain exactly one [1..1] C-CDA on FHIR Consent (identifier: http://hl7.org/fhir/StructureDefinition/ccda-consent) (CONF:2219-2011).
Control	1..1
Type	Choice of: boolean, integer, decimal, base64Binary, instant, string, uri, date, dateTime, time, code, oid, id, unsignedInt, positiveInt, markdown, Annotation, Attachment, Identifier, CodeableConcept, Coding, Quantity, Range, Period, Ratio, SampledData, Signature, HumanName, Address, ContactPoint, Timing, Reference, Meta
[x] Note	See Choice of Data Types for further information about how to use [x]