A standard symphony orchestra consists of four main groups of musical instruments: the woodwinds, brass, percussion, and strings. There are many different instruments that make up this ensemble, and each brings something unique to the table. The violin’s bow over strings carries the melody, whereas the snare drum is often used for keeping tempo and accentuating other rhythms. The french horn has a clear, mellow sound and can provide contrast to the other brass instruments, while the piccolo offers a pitch when the part to be played is especially high. Much like these core sections that must work together to produce a beautiful sounding performance, implementation teams at pMD are also comprised of different team members who have distinct talents and skillsets.
pMD is broken down into smaller account management teams who travel and go on new customer implementations together. These teams are cross-functional, meaning that the members all stem from different departments within the company: sales, operations, and development. Having people with different expertise allows for more versatility and combined knowledge when faced with a challenge!
Added Value for Onsite Implementations
Once a practice has signed on and is ready to get up and running on pMD, an implementation team will be assigned to go onsite and ensure they are set up for success. There are many moving parts that can go into a pMD rollout, especially for larger-sized groups with complex workflows. To be efficient and effective, each team member typically owns a part of the setup prior to the practice’s go-live with pMD.
The ops person can lend their expertise in logistics and planning by owning the scheduling elements for training providers and staff, along with customer success/product knowledge. Ideally, the salesperson would have previously worked with the group during the sales process, is familiar with their current workflow, and has identified the major areas where pMD can make a positive impact. Many rollouts include interfaces between pMD and other systems the practice uses, such as EMRs and practice management systems. Prior to going onsite, the dev team member can be part of building the interface and conducting testing for it to be ready for go-live. Last but not least, there is an implementation team lead who oversees the entire operation, unifies the team, and is responsible for making sure everything goes off without a hitch. Basically, the team lead is the conductor of our sinfonietta!
The most valuable part of having a cross-functional team while implementing a new group onsite is being prepared for anything that could potentially happen. Whether an interface fix needs to be made on the fly or any workflow customizations come up, the combined experience of the team allows for things to get done quickly and efficiently.
Interdepartmental Exposure & Growth Opportunities
The cross-functional team structure at pMD is pretty unique compared to other companies, especially ones with a silo mentality. Having the opportunity to collaborate with other departments that aren’t your own is less common than you might think. Bringing the different departments together has, in turn, increased communication, sparked innovation, and created a sense of team unity.
We all have our part to play, and we definitely sound better together!
To find out more about pMD's suite of products, which includes our charge capture and MIPS registry, secure messaging, clinical communication, and care navigation software and services, please contact pMD.