I'm working on a patient record web app, but I want to allow the user to store the information on their pc/mobile device until they decide to push it to a server. I looked at node-fhir-server-core, but it is not clear if a web page's localstorage could be 'plugged-in' to the architecture.
So roughly your patient record app is made up of 2 parts, the server which is a central store for all your patient's data and the app which runs on the patient's pc or phone.
Now the node fhir server being one part of your solution is separate to your web app's pages. Your web app's pages act as a client to the node fhir server and in these pages you will have to implement the localstorage solution to store the requests/data until such a time a user wants to send them to the node fhir server.
I hope that makes sense?
Related
I am working in banking sector and we have different portals for managing employee information, performance etc. I want to send push notification in mobile app from our asp.net web service when a new event (e.g. a Line Manager has to approve any pending request) occurs. How can I send notification to mobile app from our servers(where the web service has been deployed)? We don't have rights to place employee data on cloud servers or cloud databases.
Hopefully this is your request:
We don't have rights to place employee data on cloud servers or cloud
databases.
And not this:
Send Push Notification In Xamarin Forms Without Firebase
As they are entirely different. If you want to send data to Android devices you need to use Firebase for that just like you need to use Apple's servers for iOS devices. However you don't need to have any database or store data on them.
You can use PushSharp nuget if you want to minimize 3rd party server usage or some other similar solution.
Just for the record using Firebase (or other services like Azure) to send push notifications doesn't require you to place employee data on cloud servers either. Firebase and other solutions contain range of services that can be used independently and it seems that you consider them as all or nothing solution.
I have a Teams application (Tab). I am an ISV provider, and provide a multi-tenant application that is installed by customers via Teams App Store in their organizations.
How do I save settings for my application organization-wide for the customers? For example, CustomerA has installed the app and then CustomerB. I want some storage that would be unique for CustomerA and CustomerB and the app, and located in customer's environment. The settings I want to save are not per-user, but per-organization (tenant).
Somewhat similar to "App Data" folder you have in Windows Desktop for example.
Does such a storage exist? Does API for this storage exist?
A tab app is a simply a web application that you render inside of Teams. As a result, what the app does, and where and how it does it, is totally up to you. This includes any data storage you choose to have behind the scenes. For example, your tab could be built in PHP and use MySQL, or built in ASP.Net and use SQL Azure or CosmosDB. It's totally up to you, but you need to implement it yourself, as an ISV.
The important piece to differentiate clients, however, is being aware of the TenantId for each user, so you can look up which client's settings you need from the database. The most simple way to do this is simply the tid property on the Teams tab context. You can read more about that here. Unfortunately, because it's just accessed via Javascript, it's not entirely secure - for a more secure mechanism, you should be creating an Azure Application, and generating jwt tokens that you can authenticate against in your backend. It's a much more complex topic, but hopefully this answer at least gives the background you need. For more info on the security aspects (validating the token etc.), please see this question: How to restrict access to Azure Function to only allow requests from a custom Microsoft Teams App?.
I had in mind to make a website that pulls data from steam statistics to show how many players are currently playing a specific game. Is this possible or does it have to be an actual api?
If you're planning on this website only ever being a platform that displays the information you're pulling from the Steam API when users access your site, then no, you don't necessarily have to create a public-facing API.
However, if you're creating this application with the idea that other applications are going to programmatically retrieve the data you're displaying on the site, then yes, you should create an API that allows other applications to consume your data.
The best way to do the latter would be to create an independent service that consumes data from the Steam API and transforms it, then makes it available publicly (with authentication if deemed necessary). This API would then be consumed by a client that you create (your website that displays the data) as well as any other application that could make use of the data.
I am working on a product for Windows 8 that needs to perform some low-level tasks, display some UI, and communicate with an external server. I definitely need a Windows service to accomplish the low-level tasks. At the same time, I would like to use the cool features of Windows App Store apps, like push notifications, live tiles etc... for the UI. In this design, both my service and my app would communicate with my external server.
The flow would be something like: my Windows service sends some information to my server, which then sends a push notification to my App Store app.
I understand that deployment is not pretty in this scenario, but let's put that aside for now. My problem: How does the server know that the service and the app are on the same machine, and consequently linked together? i.e. When my Windows service sends information to the server, how does the server know where to send the push notification? I need is some sort of shared, unique, identifying information.
I have seen lots of discussion (usually frustrated in nature) about the lack of inter-process communication between App Store apps and desktop apps. In my case, I have two options:
Generate the exact same unique identifier in the service and in the app. This seems unlikely because apps don't seem to be able to access very much system-specific information. I'd love to be shown that I am wrong about this.
Generate a unique identifier in the server OR in the app and communicate it to the other component. Potential ways to do this:
Create the identifier in the app, save it to a file, and then access the file from the service.
Some sort of local socket solution (I've read this doesn't work, but have not tried)
Of course, option 2 seems likely to violate the Windows 8 app Certification Requirements, notably:
Windows Store apps must not communicate with local desktop
applications or services via local mechanisms, including via files and
registry keys.
Any advice would be most appreciated.
I'm not a lawyer, but if it says "via local mechanisms" then you could still possibly communicate via a cloud service as long as having both apps installed isn't necessary to have some features in the app or if you don't mean to publish the app in the store.
You could save some sort of a token in the documents folder or if your desktop app can run with appropriate permissions - it could access the local data folder of the Windows Store app to synchronize the token for use in communication with the web service.
Perhaps the user could just be asked to copy and paste a token between the two apps?
I'm interested in implementing a 'user data' backup facility for the core data sqlite database within my application.
In applications like 'simple pdf reader' you flick a switch in the app and are provided with an IP Address and port number. You then enter these details into a computer browser on the same wireless network and can then get to a web page hosted by the device. This real world example allows copy of pdf files to and from that device's app. I'd like to use the same idea to allow back up and restore of the core data database file in future versions of my app (iHeals)
I've no problem creating web pages, I'm just unsure on how to get my app to host one. Any direction is most appreciated.
Cheers,
Tim
You should take a look at implementing this framework or this one.