-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe how to query ward encounters #37
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff.
Still, how about presenting this information as an example instead? And in the introduction of the Encounter just refer to the example that then gives you more insight?
input/pagecontent/StructureDefinition-fi-base-encounter-intro.md
Outdated
Show resolved
Hide resolved
Provide more context to encounter intro with an example. Add encounter example fsh:s.
I can't get it to work. Is there an issue in sushi?
I couldn't get this text to fit nicely in the example. Putting it back to the main intro text. Added some stub paragraphs for other relvant parts, so that its clear that patients in a ward is not the only concern we are trying to adress.
I had difficulties in moving the markdown description to the example. I left my failed attempt b4ef2f1 in the commit history if there's time to debug this more later. Added another heading (which is still at todo stage) to communicate that this resource is much more than just for fetching patients in a ward. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏 Good stuff, @mikajylha!
use SHOULD instead of weak should. Fix markdown issues.
No description provided.