--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.
Same here.---- On Fri, 25 Jan 2019 09:22:24 -1000 'L.H.D. Mulder' via Cerner FHIR Developers <cerner-fhir-developers@googlegroups.com> wrote ----Same here.
On Jan 25, 2019, at 2:20 PM, Seth Merritt <mash...@gmail.com> wrote:
Same here. In our case, we will own the IP and will be working with multiple clients on an AD hoc basis.On Thursday, January 24, 2019 at 9:48:33 AM UTC-8, jol...@smcpartners.com wrote:We are developing a SMART app for a client and they have reached out to us for information on what the vetting process is to move the app from the test environment to production. We will not be listing our app in the Cerner App Gallery so we are not planning on going through the Cerner CODE submission process. Are there any available resources related to this topic?--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.To post to this group, send email to cerner-fhir-developers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.To post to this group, send email to cerner-fhir-developers@googlegroups.com.
There are several different scenarios involved here with some variance based on whether the app ownership belongs to the client organization or developer. There is also some additional considerations based on differences between provider apps and consumer apps. There is also and an additional caveat for consumer apps related to scope of use of the API in relation to Meaningful User, Stage 3 definition of Common Clinical Data Set. A lot of this is already described in some detail on our program website [1][2], but I will provide an abbreviated summary here as well.1. Application is "owned" by a Cerner client organization. In this scenario, Cerner provides a set of tools and a support process to assist clients in development, testing and access provisioning of apps to their own domains. App development and deployment is completely up to the client and no validation is needed, unless it is desired by the client. We simply assist in moving things along as needed. Sometimes clients contract with third party developers to help with actual coding with the expectation that ownership of the app at the end of development project stays with the client and there are no plans to market this app to other clients.2. Third party developer building a provider application. In the scenario developer has to enter into developer program agreement (DPA) with us [2]. DPA involves agreement on business terms and, generally, includes app validation by Cerner before it can be listed in the app gallery [3] and marketed to clients.3. Third party developer building a consumer application within the scope of MU3 CCDS definition. In this case, developer has to register the app in our system using self-service console [4] to make the app known to our API. Developer do not have to enter into a program agreement with Cerner and do not have to go through validation, unless it is desired by the developer. After app identity is created in our system developers can engage directly with our clients, who will in turn request provisioning of that app for access to their environment. (Note - This has been a topic of hot debates in a variety of forums, including this group. Our present position is that we have to have our client's approval before granting consumer app access to their environment. We intend to keep improving the overall process and tooling as we mature our product and comply with anticipated regulatory requirements.)4. Third party developer building a consumer application outside of the scope of MU3 CCDS definition (eg Appointment Scheduling). This is very similar to Scenario 2 above in that developer has to enter into program agreement with us and get the app validated, if applicable within DPA, before marketing it to our clients.-Yegor (Cerner)
On Friday, January 25, 2019 at 1:38:35 PM UTC-6, yalini sen wrote:
Same here.---- On Fri, 25 Jan 2019 09:22:24 -1000 'L.H.D. Mulder' via Cerner FHIR Developers <cerner-fhir...@googlegroups.com> wrote ----Same here.
On Jan 25, 2019, at 2:20 PM, Seth Merritt <mash...@gmail.com> wrote:
Same here. In our case, we will own the IP and will be working with multiple clients on an AD hoc basis.On Thursday, January 24, 2019 at 9:48:33 AM UTC-8, jol...@smcpartners.com wrote:We are developing a SMART app for a client and they have reached out to us for information on what the vetting process is to move the app from the test environment to production. We will not be listing our app in the Cerner App Gallery so we are not planning on going through the Cerner CODE submission process. Are there any available resources related to this topic?--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/ce3ac299-7c2c-4dce-ad52-86a073f45343%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/ce3ac299-7c2c-4dce-ad52-86a073f45343%40googlegroups.com.
Yegor,Thanks for that summary, it's very helpful.For the scenario where a developer creates an open source smart on fhir capability I imagine that can basically fall into scenario 1. In that case the Cerner site is choosing to host the application and installs it locally as if they own the application, correct?Rob
On Fri, Feb 1, 2019 at 4:03 PM Yegor Hanov (Cerner) <yegor...@gmail.com> wrote:
There are several different scenarios involved here with some variance based on whether the app ownership belongs to the client organization or developer. There is also some additional considerations based on differences between provider apps and consumer apps. There is also and an additional caveat for consumer apps related to scope of use of the API in relation to Meaningful User, Stage 3 definition of Common Clinical Data Set. A lot of this is already described in some detail on our program website [1][2], but I will provide an abbreviated summary here as well.1. Application is "owned" by a Cerner client organization. In this scenario, Cerner provides a set of tools and a support process to assist clients in development, testing and access provisioning of apps to their own domains. App development and deployment is completely up to the client and no validation is needed, unless it is desired by the client. We simply assist in moving things along as needed. Sometimes clients contract with third party developers to help with actual coding with the expectation that ownership of the app at the end of development project stays with the client and there are no plans to market this app to other clients.2. Third party developer building a provider application. In the scenario developer has to enter into developer program agreement (DPA) with us [2]. DPA involves agreement on business terms and, generally, includes app validation by Cerner before it can be listed in the app gallery [3] and marketed to clients.3. Third party developer building a consumer application within the scope of MU3 CCDS definition. In this case, developer has to register the app in our system using self-service console [4] to make the app known to our API. Developer do not have to enter into a program agreement with Cerner and do not have to go through validation, unless it is desired by the developer. After app identity is created in our system developers can engage directly with our clients, who will in turn request provisioning of that app for access to their environment. (Note - This has been a topic of hot debates in a variety of forums, including this group. Our present position is that we have to have our client's approval before granting consumer app access to their environment. We intend to keep improving the overall process and tooling as we mature our product and comply with anticipated regulatory requirements.)4. Third party developer building a consumer application outside of the scope of MU3 CCDS definition (eg Appointment Scheduling). This is very similar to Scenario 2 above in that developer has to enter into program agreement with us and get the app validated, if applicable within DPA, before marketing it to our clients.-Yegor (Cerner)
On Friday, January 25, 2019 at 1:38:35 PM UTC-6, yalini sen wrote:
Same here.---- On Fri, 25 Jan 2019 09:22:24 -1000 'L.H.D. Mulder' via Cerner FHIR Developers <cerner-fhir-developers@googlegroups.com> wrote ----Same here.
On Jan 25, 2019, at 2:20 PM, Seth Merritt <mash...@gmail.com> wrote:
Same here. In our case, we will own the IP and will be working with multiple clients on an AD hoc basis.On Thursday, January 24, 2019 at 9:48:33 AM UTC-8, jol...@smcpartners.com wrote:We are developing a SMART app for a client and they have reached out to us for information on what the vetting process is to move the app from the test environment to production. We will not be listing our app in the Cerner App Gallery so we are not planning on going through the Cerner CODE submission process. Are there any available resources related to this topic?--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.To post to this group, send email to cerner-fhir-developers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.To post to this group, send email to cerner-fhir-developers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir-developers@googlegroups.com.
There are several different scenarios involved here with some variance based on whether the app ownership belongs to the client organization or developer. There is also some additional considerations based on differences between provider apps and consumer apps. There is also and an additional caveat for consumer apps related to scope of use of the API in relation to Meaningful User, Stage 3 definition of Common Clinical Data Set. A lot of this is already described in some detail on our program website [1][2], but I will provide an abbreviated summary here as well.1. Application is "owned" by a Cerner client organization. In this scenario, Cerner provides a set of tools and a support process to assist clients in development, testing and access provisioning of apps to their own domains. App development and deployment is completely up to the client and no validation is needed, unless it is desired by the client. We simply assist in moving things along as needed. Sometimes clients contract with third party developers to help with actual coding with the expectation that ownership of the app at the end of development project stays with the client and there are no plans to market this app to other clients.2. Third party developer building a provider application. In the scenario developer has to enter into developer program agreement (DPA) with us [2]. DPA involves agreement on business terms and, generally, includes app validation by Cerner before it can be listed in the app gallery [3] and marketed to clients.3. Third party developer building a consumer application within the scope of MU3 CCDS definition. In this case, developer has to register the app in our system using self-service console [4] to make the app known to our API. Developer do not have to enter into a program agreement with Cerner and do not have to go through validation, unless it is desired by the developer. After app identity is created in our system developers can engage directly with our clients, who will in turn request provisioning of that app for access to their environment. (Note - This has been a topic of hot debates in a variety of forums, including this group. Our present position is that we have to have our client's approval before granting consumer app access to their environment. We intend to keep improving the overall process and tooling as we mature our product and comply with anticipated regulatory requirements.)4. Third party developer building a consumer application outside of the scope of MU3 CCDS definition (eg Appointment Scheduling). This is very similar to Scenario 2 above in that developer has to enter into program agreement with us and get the app validated, if applicable within DPA, before marketing it to our clients.-Yegor (Cerner)
On Friday, January 25, 2019 at 1:38:35 PM UTC-6, yalini sen wrote:
Same here.---- On Fri, 25 Jan 2019 09:22:24 -1000 'L.H.D. Mulder' via Cerner FHIR Developers <cerner-fhir...@googlegroups.com> wrote ----Same here.
On Jan 25, 2019, at 2:20 PM, Seth Merritt <mash...@gmail.com> wrote:
Same here. In our case, we will own the IP and will be working with multiple clients on an AD hoc basis.On Thursday, January 24, 2019 at 9:48:33 AM UTC-8, jol...@smcpartners.com wrote:We are developing a SMART app for a client and they have reached out to us for information on what the vetting process is to move the app from the test environment to production. We will not be listing our app in the Cerner App Gallery so we are not planning on going through the Cerner CODE submission process. Are there any available resources related to this topic?--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/8852bc9d-53a4-4336-840b-08b395272ef5%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/4938DA51-B0C6-4802-8D48-6DA91616115F%40me.com.
For more options, visit https://groups.google.com/d/optout.
Denis.
Same here.
Same here.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsubsc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsubsc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/687d5523-ff1e-4905-a373-e1f76c9e0241%40googlegroups.com.
Denis.
Same here.
Same here.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/8852bc9d-53a4-4336-840b-08b395272ef5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/687d5523-ff1e-4905-a373-e1f76c9e0241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/DBEB7B1F-4CDC-4649-9107-64DCBFF69EA5%40me.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
The decision to block patient-directed access may be local, but at least we can expect a public list of patient-access endpoints or which facilities allow patient access.Who other than Cerner is able to publish this list? As Denis says quite clearly, market leaders can play a positive and transparent role.Adrian
Denis.
Same here.
Same here.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsubsc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsubsc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/8852bc9d-53a4-4336-840b-08b395272ef5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir-developers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/687d5523-ff1e-4905-a373-e1f76c9e0241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir-developers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/DBEB7B1F-4CDC-4649-9107-64DCBFF69EA5%40me.com.
For more options, visit https://groups.google.com/d/optout.
Hi, Adrian!Your commentary is spot-on as always. Do you have an app registered in our system? We have no issue making it available to our clients for provisioning of access.
-Yegor (Cerner)
On Tuesday, February 5, 2019 at 10:08:23 PM UTC-6, Adrian Gropper wrote:
The decision to block patient-directed access may be local, but at least we can expect a public list of patient-access endpoints or which facilities allow patient access.Who other than Cerner is able to publish this list? As Denis says quite clearly, market leaders can play a positive and transparent role.Adrian
Denis.
Same here.
Same here.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/8852bc9d-53a4-4336-840b-08b395272ef5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/687d5523-ff1e-4905-a373-e1f76c9e0241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/DBEB7B1F-4CDC-4649-9107-64DCBFF69EA5%40me.com.
For more options, visit https://groups.google.com/d/optout.
--Adrian Gropper MD
PROTECT YOUR FUTURE - RESTORE Health Privacy!
HELP us fight for the right to control personal health data.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/8bf17680-d91e-4f00-aedb-c89b29b1176d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/CANYRo8g7JC7y%2BdOYp5yDJoowTnpvKnLPqY9aVHzP4%3DeymqJ34w%40mail.gmail.com.
Denis.
Same here.
Same here.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsubsc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/d3c473ea-eb0a-40d9-b704-ca9d27e01d8b%40googlegroups.com.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsubsc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/65F03019-B402-4D5F-864B-37D9C1BBE695%40me.com.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/8852bc9d-53a4-4336-840b-08b395272ef5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/687d5523-ff1e-4905-a373-e1f76c9e0241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/DBEB7B1F-4CDC-4649-9107-64DCBFF69EA5%40me.com.
For more options, visit https://groups.google.com/d/optout.
--Adrian Gropper MD
PROTECT YOUR FUTURE - RESTORE Health Privacy!
HELP us fight for the right to control personal health data.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/8bf17680-d91e-4f00-aedb-c89b29b1176d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Adrian Gropper MD
PROTECT YOUR FUTURE - RESTORE Health Privacy!
HELP us fight for the right to control personal health data.
--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-developers+unsub...@googlegroups.com.
--You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.To post to this group, send email to cerner-fhir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/CANYRo8hE0yWEzbFK4ajeD-ibs9n5LFW9Xvp6FYTfObLZy87qJA%40mail.gmail.com.
Thank You.
Denis.