Fixed elide spelling
This commit is contained in:
parent
c5b2d3cc42
commit
fb948ee3f8
@ -30,18 +30,18 @@
|
|||||||
<a name="ellipsing"> </a>
|
<a name="ellipsing"> </a>
|
||||||
<h3>Ellipsing</h3>
|
<h3>Ellipsing</h3>
|
||||||
<p>
|
<p>
|
||||||
Sometimes you want to perform more filtering than only selecting an element within your instance. You want to only show a portion of that element, hiding (ellipsing) the content you don't care about. There are two ways to do this: you can either define the specific elements you want to ellide (replace with '...'); or you can define the elements you <i>don't</i> want to ellide.
|
Sometimes you want to perform more filtering than only selecting an element within your instance. You want to only show a portion of that element, hiding (ellipsing) the content you don't care about. There are two ways to do this: you can either define the specific elements you want to elide (replace with '...'); or you can define the elements you <i>don't</i> want to elide.
|
||||||
</p>
|
</p>
|
||||||
<p>The 'ELLIDE:' filter can only be specified once, but with FHIRPath '|', you can express as many elements as you like. For example, <code>{% raw %}{% fragment Patient/example XML BASE:name.where(use='official').first() ELLIDE:use|given[1]|period %}{% endraw %}</code> will look like this:</p>
|
<p>The 'ELIDE:' filter can only be specified once, but with FHIRPath '|', you can express as many elements as you like. For example, <code>{% raw %}{% fragment Patient/example XML BASE:name.where(use='official').first() ELIDE:use|given[1]|period %}{% endraw %}</code> will look like this:</p>
|
||||||
{% fragment Patient/example XML BASE:name.where(use='official').first() ELLIDE:use|given[1]|period %}
|
{% fragment Patient/example XML BASE:name.where(use='official').first() ELIDE:use|given[1]|period %}
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
'EXCEPT:' works slightly differently. With Except you identify the elements to retain (be unellided) but you can also specify a descendant 'BASE:' element those expressions are evaluated within. For example, the following expression will return the patient showing only id an names, and within name, will ellide everything except the family name: <code>{% raw %}{% fragment Patient/example XML EXCEPT:id|name EXCEPT:family BASE:name %}{% endraw %}</code>
|
'EXCEPT:' works slightly differently. With Except you identify the elements to retain (be unelided) but you can also specify a descendant 'BASE:' element those expressions are evaluated within. For example, the following expression will return the patient showing only id an names, and within name, will elide everything except the family name: <code>{% raw %}{% fragment Patient/example XML EXCEPT:id|name EXCEPT:family BASE:name %}{% endraw %}</code>
|
||||||
</p>
|
</p>
|
||||||
{% fragment Patient/example XML EXCEPT:id|name EXCEPT:family BASE:name %}
|
{% fragment Patient/example XML EXCEPT:id|name EXCEPT:family BASE:name %}
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
The overall syntax for fragments is as follows:
|
The overall syntax for fragments is as follows:
|
||||||
<code>{% raw %}{% fragment [resource]/[id] [XML|JSON] (BASE:[base FHIRPath])? (ELLIDE:[ellide elements path])? (EXCEPT:[except elements FHIRPath] (BASE:[except base FHIRPath])?)* %}{% endraw %}</code>
|
<code>{% raw %}{% fragment [resource]/[id] [XML|JSON] (BASE:[base FHIRPath])? (ELIDE:[elide elements path])? (EXCEPT:[except elements FHIRPath] (BASE:[except base FHIRPath])?)* %}{% endraw %}</code>
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user