CDS Hooks
3.0.0-ballot - R3 Normative Ballot
CDS Hooks, published by Clinical Decision Support WG. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/cds-hooks/ and changes regularly. 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 |
| 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..* |
| 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 |
| 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..* |
| 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 |