eReferral Spec Development work stream

Meeting Minutes - eReferral Working Grouo:
May 25, 2023, 11:00am
=================
Agenda:
1. Progress on publishing update

2. Conformance Testing & Validation Project update
- Ion - Standardize validation around SmileCDR
- Gap- Missing artifacts to generate reports based on validation conformance testing. Standards team is still deciding what’s the best tooling approach for this. Don’t known when a decision is going to be made.
- 2 options contemplating - AEGIS, or SmileCDR instance dedicated to conformance testing
- Goal is to provide something that vendors can use

3. Federate directory (10min)
- Have a dedicated session Russ B to schedule.
- Include Ion, Russ, Jon, Radhinka, Alex from OH , Tony Mitchell
-How to state authority on some fields - this is an important use case to think through. Some data is more commercial in data than regulatory in nature. How to say this is a “partial” master

4. Review issues

5. Branching and forwarding
1. Have a meeting - Russ B to schedule
2. Share collaborative document

Meeting Minutes - eReferral Working Grouo:
May 25, 2023, 11:00am
=================
Agenda:
1. Progress on publishing update

2. Conformance Testing & Validation Project update
- Ion - Standardize validation around SmileCDR
- Gap- Missing artifacts to generate reports based on validation conformance testing. Standards team is still deciding what’s the best tooling approach for this. Don’t known when a decision is going to be made.
- 2 options contemplating - AEGIS, or SmileCDR instance dedicated to conformance testing
- Goal is to provide something that vendors can use

3. Federate directory (10min)
- Have a dedicated session Russ B to schedule.
- Include Ion, Russ, Jon, Radhinka, Alex from OH , Tony Mitchell
-How to state authority on some fields - this is an important use case to think through. Some data is more commercial in data than regulatory in nature. How to say this is a “partial” master

4. Review issues

5. Branching and forwarding
1. Have a meeting - Russ B to schedule
2. Share collaborative document

Meeting Minutes - eReferral Working Grouo:
May 25, 2023, 11:00am
=================
Agenda:
1. Progress on publishing update

2. Conformance Testing & Validation Project update
- Ion - Standardize validation around SmileCDR
- Gap- Missing artifacts to generate reports based on validation conformance testing. Standards team is still deciding what’s the best tooling approach for this. Don’t known when a decision is going to be made.
- 2 options contemplating - AEGIS, or SmileCDR instance dedicated to conformance testing
- Goal is to provide something that vendors can use

3. Federate directory (10min)
- Have a dedicated session Russ B to schedule.
- Include Ion, Russ, Jon, Radhinka, Alex from OH , Tony Mitchell
-How to state authority on some fields - this is an important use case to think through. Some data is more commercial in data than regulatory in nature. How to say this is a “partial” master

4. Review issues

5. Branching and forwarding
1. Have a meeting - Russ B to schedule
2. Share collaborative document

Meeting Minutes - eReferral Working Grouo:
May 25, 2023, 11:00am
=================
Agenda:
1. Progress on publishing update

2. Conformance Testing & Validation Project update
- Ion - Standardize validation around SmileCDR
- Gap- Missing artifacts to generate reports based on validation conformance testing. Standards team is still deciding what’s the best tooling approach for this. Don’t known when a decision is going to be made.
- 2 options contemplating - AEGIS, or SmileCDR instance dedicated to conformance testing
- Goal is to provide something that vendors can use

3. Federate directory (10min)
- Have a dedicated session Russ B to schedule.
- Include Ion, Russ, Jon, Radhinka, Alex from OH , Tony Mitchell
-How to state authority on some fields - this is an important use case to think through. Some data is more commercial in data than regulatory in nature. How to say this is a “partial” master

4. Review issues

5. Branching and forwarding
1. Have a meeting - Russ B to schedule
2. Share collaborative document

Thanks for your feedback and thoughts on that, Tim. That is helpful.

If there isn't currently a spot for Received Date, another thought, along with the possibility of adding to Task, is to possibly add Received Date as an extension to Service Request. It looks like there are some other Wait Time concepts that have been added as extensions there, i.e. DARC and DART.

Interesting. My first thought was to use the "authored on" field in the service request, but that doesn't seem to quite fit your use case.

Instead, this is a "task" concept about when the receiving system into or past one of the statuses that represent your concept of received.

I think that this would require an extension on the Task resource.