Skip to content

Commit f001351

Browse files
2 parents 79f1c97 + aec4e9f commit f001351

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/azure-health-insights/radiology-insights/recommendation-inference.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: JanSchietse
77
manager: JoeriVDV
88
ms.service: azure-health-insights
99
ms.topic: overview
10-
ms.date: 12/12/2023
10+
ms.date: 5/21/2025
1111
ms.author: JanSchietse
1212
---
1313

@@ -147,7 +147,7 @@ An example of a follow-up recommendation (without token extensions):
147147
"isHedging": false
148148
}
149149
```
150-
> ## Sentences
150+
## Sentences
151151
Next to the token extensions, there can be an extension containing sentences. This behavior is switchable; the sentences will only be generated if option "provideFocusedSentenceEvidence" in "FollowupRecommendationOptions" is set to true. In practice, this will only be set to true if the customer is mPower or Powerscribe.
152152

153153
Example:
@@ -167,22 +167,22 @@ Fields `isConditional`, `isOptions`, `isGuideline`, and `isHedging` are set to t
167167
- `isOptions`: is also for conditional input.
168168
- `isGuideline`”` means that the recommendation is in a general guideline, for example, "Patients over 50 with obesity should have their blood glucose checked yearly."
169169

170-
> ## effectiveDateTime and effectivePeriod
170+
## effectiveDateTime and effectivePeriod
171171
Field `effectiveDateTime` will be set when the procedure is recommended to be done at a specific point in time, for example, "next Wednesday". Field `effectivePeriod` is set if a specific period is mentioned, with a start and end datetime. For example, for "within 6 months", the start datetime will be the date of service, and the end datetime will be the day six months after that. (Note that "in 6 months from now" is interpreted as a specific point in time, not a period.)
172172

173-
> ## findings
173+
## findings
174174
If set, field `findings` contains one or more findings that have to do with the recommendation. For example, a leg scan (procedure) can be recommended because of leg pain (finding).
175175
Every array element of field `findings` is a RecommendationFinding. `RecommendationFinding.finding` has the same information as a `FindingInference.finding` field (see [Finding Inference](finding-inference.md)).
176176
For field `RecommendationFinding.RecommendationFindingStatus`, see the OpenAPI for the possible values.
177177
Field `RecommendationFinding.criticalFinding` is set if a critical result is associated with the finding. It then contains the same information as `CriticalResultInference.criticalResult` (see [Critical Result](critical-result-inference.md).)
178178

179-
> ## Recommended procedure
179+
## Recommended procedure
180180
Field `recommendedProcedure`: it's either a generic procedure recommendation, or an imaging procedure.
181181

182-
> ### Generic procedure recommendation
182+
### Generic procedure recommendation
183183
The kind is `genericProcedureRecommendation`. The description is either "MANAGEMENT PROCEDURE (PROCEDURE)" or "CONSULTATION (PROCEDURE)". The code only contains an extension with tokens.
184184

185-
> ### Imaging procedure
185+
### Imaging procedure
186186
The kind is `imagingProcedureRecommendation`.
187187
Field `imagingProcedures` contains an array with one element of type ImagingProcedure. This type has the following fields, the first two of which are always filled:
188188
- `modality`: a CodeableConcept containing at most one coding with a SNOMED or RadLex code.

0 commit comments

Comments
 (0)