It is Grahame as a great FHIR product manager who asks the FHIR community to provide information on how to build FHIR Connectathon. I started writing a few lines, but realized that I could say a lot more than a few lines. (Yes, I know … Blah Blah Blah)
IHE is connected to connectathons for nearly 20 years (first in 1999 at the Department of Radiology). The IHE does not invent the concept of Connectathon. I joined TCP, IP, UDP, NFS, TELNET, and FTP connections in the late 1980’s. This is almost the same event. I have a detailed article what is Connectathon, and not … please check it out. What is Connectathon? I also wrote how good it is to see how FHIR Connectathon changes.
I think that IHE and FHIR should be as diverse as possible, but there will be obviously there will be overlaps. Each of them now occupies a unique position so that the involved can see each other clearly. However, it is difficult for the difference in the outside world. This view should be considered as an important factor for the outside world. If common consumer and connectathon are unintelligible or confused, there is no value or explanation.
This does not mean that disturbances should be avoided, but should be made consciously and clearly. Today, FHIR Connectathon is more than a hackathon, and that’s exactly what the FHIR community needs. Value now: a quick (test) test of specifications that provides the foundation for application development ideas, a safe place to share and push ideas. An important part of this success is that they are short (1.5-2 days), very low (compared to IHE Connectathon) and very informal (compared to IHE Connectathon). These are the strengths of FHIR Connectathon today, which we should not forget.
The mature part of this FHIR community is ready to take a new step. I do not think that the new step is on the way to what IHE Connectathon is doing and far from being dependent (which is the IHE Connectathon for some tracks as well). The more mature part of the FHIR community needs a more formal place to play, but things like FHIR’s Dev Day can satisfy that need?
If possible, work with IHE Connectathon. Use the same tools as possible. Use the same process and space for events as much as possible.
IHE should focus on the use of multiple use cases and cases of using a particular domain. The IHE should focus on the general procedures documented in the Profile or Implementation Guide.
FHIR should focus on cases of using FHIR’s sole use and are generally available for re-use. FHIR Connectathon will be the ideal location for the model to explore, develop a concept and develop consensus.
FHIR Connectathon needs to further enhance the complexity of the situations and include small situations in major situations. Sophisticated analysis of design scenarios so that the units can be completely disabled to make BDD or TDD. The standard “standard” beyond what we now see as “standard” is not just “coding” but it affirms the building and prohibits it.
This does not mean that FHIR Connectathon does not run a full workflow from start to finish. That does not mean that IHE will not be done like Hackathon. Overlap will continue, it should be clear.
an eye on the goal of Connectathon
For the establishment of Connectathon standards is a way to end the standard. Both IHE and FHIR are related to the required portions of their maturity rating.
The purpose of Connectathon for a participant is to gain experience in dealing with his potential partner in the future with a real exchange. If you focus on testing a safe place like Connectathon, you can push the boundaries of your software. The supplement is the trust that a client, if he or she needs your program to talk to a particular colleague, has great confidence that he will work right away, and if he has no experience, his answer, including personal relationship he has the program. ATNA audit has been redesigned with FHIR as an AuditEvent resource.