This page is part of the HL7 Tools Extension IG (v0.8.0: Release - Informative) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
| Page standards status: Informative | Maturity Level: 1 | 
Definitions for the CDSHooksExtensions logical model.
Guidance on how to interpret the contents of this table can be foundhere
| 0. CDSHooksExtensions | |
| Definition | A JSON object that has properties where the names are defined by the extension definitions Base definition for all types defined in FHIR type system. | 
| Short | Object that has Named Extension PropertiesBase for all types and resources | 
| Comments | Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined | 
| Control | 0..1* | 
| Is Modifier | false | 
| Logical Model | Instances of this logical model are not marked to be the target of a Reference | 
| 2. CDSHooksExtensions.extension | |
| Definition | An extension where the name is defined by the extension definition, and the extension definition is of any type (including primitives, though the 'id' element cannot be represented for primitives) | 
| Short | An extension of any type | 
| Control | 0..* | 
| Type | Base | 
| Extension Style | This element can be extended by named JSON elements | 
Guidance on how to interpret the contents of this table can be foundhere
| 0. CDSHooksExtensions | |
| Definition | A JSON object that has properties where the names are defined by the extension definitions | 
| Short | Object that has Named Extension Properties | 
| Comments | Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined | 
| Control | 0..1 | 
| Logical Model | Instances of this logical model are not marked to be the target of a Reference | 
| 2. CDSHooksExtensions.extension | |
| Definition | An extension where the name is defined by the extension definition, and the extension definition is of any type (including primitives, though the 'id' element cannot be represented for primitives) | 
| Short | An extension of any type | 
| Control | 0..* | 
| Type | Base | 
| Extension Style | This element can be extended by named JSON elements | 
Guidance on how to interpret the contents of this table can be foundhere
| 0. CDSHooksExtensions | |
| Definition | A JSON object that has properties where the names are defined by the extension definitions | 
| Short | Object that has Named Extension Properties | 
| Comments | Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined | 
| Control | 0..1 | 
| Is Modifier | false | 
| Logical Model | Instances of this logical model are not marked to be the target of a Reference | 
| 2. CDSHooksExtensions.extension | |
| Definition | An extension where the name is defined by the extension definition, and the extension definition is of any type (including primitives, though the 'id' element cannot be represented for primitives) | 
| Short | An extension of any type | 
| Control | 0..* | 
| Type | Base | 
| Extension Style | This element can be extended by named JSON elements |