Skip to content

Commit 5ff7b6d

Browse files
committed
Add instructions on including profile when creating ActivityDefinitions
1 parent 82a6322 commit 5ff7b6d

1 file changed

Lines changed: 9 additions & 4 deletions

File tree

docs/src/process-development/api-v2/guides/creating-activity-definitions.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,24 @@ It is divided into steps for each of the main components of ActivityDefinitions:
1616

1717
*We will assume you know how to translate [ElementDefinitions](https://www.hl7.org/fhir/R4/elementdefinition.html) to actual elements in a FHIR resource. If you do not, you might want to check out the guide on [creating Task resources](../guides/creating-task-resources-based-on-a-definition.md) first.*
1818

19-
#### 1. Read Access Tag
20-
Let us start out with an empty [ActivityDefinition](../fhir/activitydefinition.md):
19+
#### 1. Profile and Read Access Tag
20+
Let us start out with an empty [ActivityDefinition](../concepts/fhir/activitydefinition.md):
2121
```xml
2222
<ActivityDefinition xmlns="http://hl7.org/fhir">
2323

2424
</ActivityDefinition>
2525
```
26-
27-
The first element in DSF FHIR resources is always the [Read Access Tag](../dsf/read-access-tag.md). It describes who is allowed to read this resource through the DSF FHIR server's REST API. You can learn more complex configurations of the [Read Access Tag](../dsf/read-access-tag.md) in [this guide](../dsf/read-access-tag.md). In this case, we will allow read access to everyone:
26+
The first elements to be added to [ActivityDefinitions](../concepts/fhir/activitydefinition.md) are the profile and the read access tag as part of the `meta` element.
27+
The profile element includes the URL of the profile the [ActivityDefinition](../concepts/fhir/activitydefinition.md) should conform to.
28+
In case of the DSF this is always `http://dsf.dev/fhir/StructureDefinition/activity-definition`.
29+
The [Read Access Tag](../concepts/dsf/read-access-tag.md) describes who is
30+
allowed to read this resource through the DSF FHIR server's REST API. You can learn more complex configurations of the
31+
[Read Access Tag](../concepts/dsf/read-access-tag.md) in [this guide](../concepts/dsf/read-access-tag.md). In this case, we will allow read access to everyone:
2832

2933
```xml
3034
<ActivityDefinition xmlns="http://hl7.org/fhir">
3135
<meta>
36+
<profile value="http://dsf.dev/fhir/StructureDefinition/activity-definition" />
3237
<tag>
3338
<system value="http://dsf.dev/fhir/CodeSystem/read-access-tag" />
3439
<code value="ALL" />

0 commit comments

Comments
 (0)