Encounter #30
Locked
dt-r
started this conversation in
AU Core R1 Resource Priority List - CLOSED
Replies: 4 comments 4 replies
-
Should Encounter be a place to recode progress/visit notes? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Consider pushing Encounter.reasonCode binding to FHIRWG for AU Base with a recommendation. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Why have we made period mandatory whereas US Core hasn't? This will limit the use of core encounter when the period isn't known. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Why can't the description be captured in the narrative? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Upvote for inclusion of a Resource Profile of Encounter Resource in AU Core Release 1.
Comment if you think we need a different profile to AU Core Encounter, or if there is a need for an additional Encounter profile in AU Core.
AU Core Encounter profile would set minimum expectations for a Encounter resource to record, search, and fetch basic encounter information for a patient.
AU Core Encounter should be based on the AU Base Encounter profile and identify the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Encounter resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
Beta Was this translation helpful? Give feedback.
All reactions