From the doctor's office to the patient's home! The patient will be the center of the entire process. The key issue is reverse the concept of telemedicine. Dear Patient P! Analyzing your data, we would like to schedule a face-to-face consultation with Specialist Doctor E to avoid (seek to reduce) the risk of the occurrence of a certain disease D. The main challenge is that health is not explicitly defined in the diagnostic process. It is considered only as a complement to the disease. People mistakenly and invariably think that if I'm not sick, I'm healthy!
https://architecture.synthesis.eco.br/
All transactions must respect access, privacy, and intellectual rights. This universe of synthesis is built on demand, generated by the community itself, respecting the interests of each doctor and consequently their patients. The best practices related to the control of rights and information security, already used and specific, defined in the LGPD, GDPR, and HIPAA, must be followed. It is important to reinforce the observation that all intelligence must be applied anonymously. Used only to look for patterns and relationships between events that would be within a single privately stored universe. For example, a medical record could be in a unified database with all of its information, but the only person who would know the patient's name would be the doctor responsible for the diagnostic information. In this case, the meaning of the concept of “synthesis” changes. Occasionally, the aforementioned concept becomes an anonymization process based on the application of algorithms and cryptographic techniques to generate data with the same statistical standard as the original data. Without unlocking keys, the data is an indecipherable code for anyone using it. Note that there are several data synthesis techniques. In some cases, information such as dates must be kept unchanged, as certain analyses may need to know the person's age, for example. The entire process is controlled by the aforementioned protocols: LGPD, GDPR, and HIPAA. Each study is a specific case with its respective needs! But the fact is that a technological leap has occurred in recent years, due to the challenge of overcoming the pandemic.
22 Jul 2024
synthesis architecture e2
https://architecture.synthesis.eco.br
The super app synthesis.clinic is capable of performing the same functions as a conventional electronic medical record, such as anamnesis, physical examination, consultation of the results of laboratory tests and patient images, even medical management and diagnosis . The system has a single interface for a web platform or mobile application, using the Python programming language to develop the application layer logic.
In this scenario, Vercel's cloud platform is proposed together with Next.JS, so that the model is hosted and fed through the data that will come from Aura DB. In the cloud, there are three information input ports: messages from the mobile interface; information through the Back Endi server APIs; and the Next/React client interface.
The development of the presentation layer uses the Chakra graphics component library to assist with user interface layout and components. This project aims to integrate the clinic (or hospital) system and the mobile application through web services, so that data traffic between the systems can be carried out.
The data layer is integrated through Cypher queries (CQL) applied directly to the graphs through paths. A classic example of a CQL query is the Shortest Path (shortest path between two nodes or concepts). The technological leap of a Graph DB is being able to perform queries that are impossible for conventional Relational banks for more complex cases, such as the itinerary of a transcontinental air trip. In this dimension, even the best relational DBMS such as Oracle and SQL server or Postgres cannot process certain queries. This fact is explained by the computational paradigm. Graph processing is more efficient for complex data. GDS (Graph Data Science) contributes to this point, creating specific properties in the nodes with metrics of their processing. This allows synchronization with the D3.js (Popoto) and NeoVis visualization APIs that will work on the intelligent Timeline generated by GDS. The knowledge synthesis project's interactive predictions and simulations utilize this innovative concept.
22 Jul 2024
synthesis architecture e1
https://architecture.synthesis.eco.br
We believe that we can extend our super app concept to other areas, in addition to health, creating a unified console between the person and the environment: Next.js (Vercel); Neo4J (Aura DB); Cloud (GCP) for Apache (Spark/Kafka/Arrow); and Digital Ocen apps for AI with Python. In short, what a company would have the technology. It's annoying that people don't know the importance of having a professional technological structure that could be purchased for the price of a pizza a month. Instead of giving up your data on free platforms that win at both ends (client and content producer), they explicitly sell data that is not yours. And everything is fine. It is free! I might buy one more pizza this month. Culture is important, we believe that the current moment is a watershed.
An important point regarding the modeling aspect of Graph DB schemas is their modification, based on the parameters targeted by the models built through GDS (Graph Data Science). Custom schemas can be created with nodes containing properties previously stored in relationships. This is because the Knowledge Engineer has specific needs.
Customizations allow you to create the ML Pipeline and training or testing models in GDS. The records will be defined, according to analysis seeking to standardize information specified by the HL7 communication protocol for health systems. The file in the protocol model generated for communication will, therefore, have a single item, the patient, or the map with all its respective information related to the Graph DB, forming the structure of its schema adaptable to the structure of a JSON file. This is considered the main idea taken from the HL7 communication protocol, previously mentioned elsewhere.
This process allows all relationships and conventional entities oriented to just a single record to be identified, providing the ability to integrate with external knowledge bases through mapping the relationship between internal and external concepts made possible by APIs for connecting to Graph DBs in the health sector, available at synthesis.clinic
The electronic medical record mobile application is integrated with the cloud through a backend project, which allows registering the application using an “API key” identifier from the Next.JS project. Communication is carried out by queries defined within the control methods with the function of carrying out the process of searching/sending data for exchanged messages. Subsequently, its persistence is initiated from the integrated synthesis.eco.br web console (server and client) in the Next.JS language and then recorded in the cloud and finally synchronized in the Graph DB Aura, assembling the map of concepts and relationships that will form part of the patient's medical record.
Reach and audience
Public platform figures. Ratings count people who left a rating, not total listeners.
Spotify
5.0 / 5
1 ratings
Contact graph.md
Guest appearances
Books guests
Based on episode analysis; this does not confirm that the show is currently accepting guests.
Host of graph.md?
Claim your podcast to manage its listing and keep your show details accurate.
Pod Engine is an independent podcast discovery and analytics service and is not affiliated with or endorsed by this podcast. Artwork and show content belong to their owners. Full legal notice.
Explore this show Podcast research with Pod Engine
