Faites-nous part de vos impressions sur le Serveur terminologique, et aidez-nous à améliorer nos services! Vous avez jusqu’au 3 décembre 2024 pour répondre au sondage. Votre avis nous intéresse!
En savoir plus >
- Mike updated community on new approach to batching profiles by domain and reviewing them in new, separate streams which will also involve members reaching out to SMEs to review the profiles
- Entities stream: can be reviewed and changes proposed by system architects and DBAs, doesn’t have to be clinical SMEs
- Suggestion to maintain a general Profiling stream meeting to give a way to harmonize the proposed changes made in the different streams
- Reminder that we should ensure that there are some core use cases that wrap around the core profiles
- Eg: Medication batch of profiles, use cases these profiles must support well: prescribing, MedRec, etc
Profiling
- View that SnomedCT can be put as the preferred value set for data elements (in context of Results profile discussion)
Next Steps
- ACTION ITEM: Mike to put out a call for volunteers to lead the sub streams of batch profile reviewing
- Shamil volunteered to help coordinate the entities stream
- Shamil may be able to enlist some folks to get involved with the Medications stream
- Support for passing on the low FMM profiles and focus on the more widely used ones
- Request to not have sub streams meeting at the same time; allows members to join multiple streams
- ACTION ITEM: Mike to make a slide / visual that shows the new proposed breakdown and the particulars (how many streams, focused on what each, meeting when, how to get SME input, etc.)
- ACTION ITEM: Mike to post in forum to notify Community that we will be testing out the approach of using part of the Solution Architecture bi-weekly meetings for additional time to discuss the topics of the Governance Stream
The draft agenda for this Friday's call is to firstly provide an update on the approach for securing SME input and proposed changes for the profiles left to review (especially the more clinical ones). Tied into this is a suggestion put forward by Shamil about how to more efficiently tackle the remaining profiles by approaching them as sub-groups (to be elaborated on during the call). The plan is to then field a set of proposed changes for the Results profile. These can be viewed in detail on the GitHub issue log: github.com/scratch-fhir-profiles/CA-Core/issues