Encounter service event #40
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 6 commits
January 26, 2023 10:22
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.
added 2 commits
January 30, 2023 18:13
First bite at settling the relationship between Kanta Palvelutapahtuma and encounter.
a867edb to
ff789ec
Compare
mrinnetmaki
approved these changes
Jan 30, 2023
|
|
||
| * extension contains ServiceEvent named serviceEvent 0..1 | ||
|
|
||
| Extension: ServiceEvent |
There was a problem hiding this comment.
I would have thought palvelutapahtumatunniste to be a specific kind of an Identifier.
| Usage: #example | ||
| * id = "id-for-visit" | ||
| * identifier.use = #usual | ||
| * identifier.value = "id-for-visit" |
There was a problem hiding this comment.
The usual identifier should be
the identifier recommended for display and use in real-world interactions.
I don't think id-for-visit is such an identifier.
I do think a palvelutapahtumatunniste might be...
| Description: "An example of a FI Base encounter where a patient is currently receiving care at a ward." | ||
| Usage: #example | ||
| * id = "id-for-ward-encounter" | ||
| * identifier.use = #usual |
There was a problem hiding this comment.
Same comment as for the ambulatory example.
|
|
||
| The scope of palvelutapahtuma is [described](https://www.kanta.fi/jarjestelmakehittajat/liite-2-palvelutapahtumien-esimerkkeja) | ||
| in Kanta-documentation (in finnish). It's scope is not the same as encounter's. Encounter and | ||
| Palvelutapahtuma will overlap as concepts (depending on implementation). |
There was a problem hiding this comment.
We have palvelutapahtuma both capitalized and not.
How about not capitalizing it, but always putting it in italics?
|
|
||
| For example a laboratory information system may have it's own Kanta Medical Records capabilities | ||
| and will archive lab results directly to Kanta. It receives encounter id in SMART App Launch | ||
| context. Laboratory system can resolve Palvelutapahtuma`s OID identifier by fetching the encounter |
There was a problem hiding this comment.
Wrong kind of an apostrophe here...
|
|
||
| Encounters can be grouped together to form larger administrative 'periods' by using the `partOf` | ||
| element. Vendor implementations vary and it's difficult to pinpoint which level (if any) would | ||
| match Palvelutapahtuma. For best interoperability we should *not* assume Palvelutapahtuma corresponds |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First bite at Palvelutapahtuma